Show HN: Mount Unix system into Common Lisp image

Wow, that&#x27;s crazy O_o<p>Related:<p>- Lish allows to mix&amp;match shell and Lisp code, with regular syntax. <a href="https:&#x2F;&#x2F;github.com&#x2F;nibbula&#x2F;lish&#x2F;">https:&#x2F;&#x2F;github.com&#x2F;nibbula&#x2F;lish&#x2F;</a><p><pre><code> $ echo ,*package* #&lt;PACKAGE &quot;LISH-USER&quot;&gt; $ (defun hello (name) (format t &quot;hello ~a!!~&amp;&quot; name)) $ (hello &quot;me&quot;) hello me!! NIL $ (hello &quot;me&quot;) | wc -w =&gt; 2 </code></pre> It is usable. Interactive commands like sudo and htop work, some like less and fzf don&#x27;t. So it ships a pager, `view`. It has a directory mode, a Lisp REPL with a debugger, completion…. It is not done, the author keeps hacking on it. Hackers invited to have a look.<p>- SHCL is a posix-like shell written in CL. <a href="https:&#x2F;&#x2F;github.com&#x2F;bradleyjensen&#x2F;shcl">https:&#x2F;&#x2F;github.com&#x2F;bradleyjensen&#x2F;shcl</a> (it doesn&#x27;t have completion. Not active.)<p><a href="https:&#x2F;&#x2F;github.com&#x2F;CodyReichert&#x2F;awesome-cl#shells-shells-interfaces">https:&#x2F;&#x2F;github.com&#x2F;CodyReichert&#x2F;awesome-cl#shells-shells-int...</a>

One of those &quot;I wonder what it&#x27;d be like if someone made that&quot;, and then someone _does_ make that, kudos!<p>Also, `defile` is a great name for a macro :-)

Neat. Funny enough I&#x27;ve recently considered writing sort of the exact opposite of this - a FUSE FS that maps every package and symbol of a running lisp image into the filesystem, so that the value of variables could be read&#x2F;written from outside, fbound symbols would be marked executable and &quot;callable&quot; from unix by running them (via some weird shebang hack, I guess), etc.

Related: <a href="https:&#x2F;&#x2F;scsh.net&#x2F;about&#x2F;what.html" rel="nofollow">https:&#x2F;&#x2F;scsh.net&#x2F;about&#x2F;what.html</a>

One of the examples in the readme is this<p>Counting number of files<p><pre><code> &#x2F;Users&#x2F;kchan&gt; (cd quicklisp&#x2F;local-projects&#x2F;unix-in-lisp) &#x2F;Users&#x2F;kchan&#x2F;quicklisp&#x2F;local-projects&#x2F;unix-in-lisp&gt; (pipe (wc -l) (ls)) 9 </code></pre> Personally, I would want the top level parens to be implicit so I could write<p><pre><code> &#x2F;Users&#x2F;kchan&gt; cd quicklisp&#x2F;local-projects&#x2F;unix-in-lisp &#x2F;Users&#x2F;kchan&#x2F;quicklisp&#x2F;local-projects&#x2F;unix-in-lisp&gt; </code></pre> This removes what could be trivial, but for a basic `cd`, I don&#x27;t want to have to remember parens every time. Optionally having those parens would be nice for when they&#x27;re needed, but for basic use-cases I&#x27;d rather not.