Chris's Wiki :: blog/links/DmenuChanges Commentshttps://utcc.utoronto.ca/~cks/space/blog/links/DmenuChanges?atomcommentsDWiki2013-08-15T04:38:49ZRecent comments in Chris's Wiki :: blog/links/DmenuChanges.By Chris Siebenmann on /blog/links/DmenuChangestag:CSpace:blog/links/DmenuChanges:a01e5f6c0860b9c357f1901686816b8ef5348b74Chris Siebenmann<div class="wikitext"><p>The short answer is that <code>dmenu</code> can't do any of that without making
large assumptions about how it's being used. Dmenu is a general tool,
not just a program launcher.</p>
</div>2013-08-15T04:38:49ZFrom 121.45.239.165 on /blog/links/DmenuChangestag:CSpace:blog/links/DmenuChanges:54c6bd661dcb142ec8c642605ddaabf6ed9e6c0eFrom 121.45.239.165<div class="wikitext"><p>My shell is bash, so I changed the last line of <code>dmenu_run</code> from:</p>
<pre>
) | ${SHELL:-"/bin/sh"} &
</pre>
<p>to:</p>
<pre>
) | /bin/ash &
</pre>
<p>because the purist in me rebels at running everything from a bloated bash shell.</p>
<p>That same purist wishes dmenu would test the executable with <code>file</code> and <code>exec</code> it if it doesn't need a shell. (Despite now having 4GB of memory available, I still retain OCD memory constraint instincts from 1990. Yes, I have a grey beard...) </p>
<p>I dunno, there is just something <em>wrong</em> with running executables from a shell.</p>
<p>Nick Coleman</p>
</div>2013-08-15T03:46:15Z