<story><title>lsix: ls for images</title><url>https://github.com/hackerb9/lsix</url></story><parent_chain></parent_chain><comment><author>isomorphic</author><text>Aside: Although iTerm2 (on macOS) doesn&amp;#x27;t appear to work with this, iTerm2 actually supports full-color inline images, and has an &amp;quot;imgls&amp;quot; script which does something similar.  (There&amp;#x27;s also &amp;quot;imgcat&amp;quot;.)&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.iterm2.com&amp;#x2F;documentation-images.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.iterm2.com&amp;#x2F;documentation-images.html&lt;/a&gt;</text></comment>
<story><title>lsix: ls for images</title><url>https://github.com/hackerb9/lsix</url></story><parent_chain></parent_chain><comment><author>userbinator</author><text>&lt;i&gt;You can also specify filenames and, of course, use shell wild cards&lt;/i&gt;&lt;p&gt;&lt;i&gt;However, some may be slow to render (like PDF), so lsix doesn&amp;#x27;t show them unless you ask specifically.&lt;/i&gt;&lt;p&gt;Regardless of the justification, I don&amp;#x27;t think creating such extra exception&amp;#x2F;edge-case behaviours are ever a good idea in a commandline tool like this. The equivalent in regular ls would be something like not showing more than X files &amp;quot;unless you ask specifically&amp;quot; --- which would just create more confusion than anything. As someone who has used the commandline for many years, one property which needs to be present for good usability is &lt;i&gt;consistency&lt;/i&gt;. Having a bunch of edge-cases and special behaviours makes a tool hard to use for anything but the most extremely basic of operations.</text></comment>