Re: [hackers] [dmenu][PATCH] Replace dmenu_run shell with executed application

From: Jan Bessai <>
Date: Sun, 10 Feb 2019 12:20:44 +0100

On 10.02.19 11:40, Leonardo Taccari wrote:
> The user's $SHELL is no longer used and what can be typed in
> `dmenu_run' is now restricted, (I don't know how usual is but
> sometimes I use `|' and other shell commands in dmenu_run).

Is there a good reason not to explicitly run a shell then? I.e. launch

sh -c "printf 'foo' | cat"

instead of

printf 'foo' | cat

and have just the shell executing these commands wait on them instead of
the shell executing dmenu? I guess it is a matter of convenience (but
there might be something I overlook).

For those interested, in my setup I've put the patched script on my path
instead of (before) dmenu_run, which works quite nicely to get the
behavior I want/like. A good compromise can also be to have both
(dmenu_run and dmenu_run_shell).

Anyhow, I'll leave it at that and hope some people on this list like the
useful way to cut the number of lingering processes in your system down
immensely when launching almost everything via dmenu :)
If you should happen to decide differently and include the patch just
post here and I can help with the man page cleanup.
Received on Sun Feb 10 2019 - 12:20:44 CET

This archive was generated by hypermail 2.3.0 : Sun Feb 10 2019 - 12:24:22 CET