Re: [dev] dmenu and dwm: is exec really needed

2016-04-28 Thread Martti Kühne
Greg, if you want to limit your dmenu to executables, use this line instead of the pipe-to-$SHELL: exec $(dmenu_path | dmenu "$@") I left the substitution unquoted, so you can still pass arguments to commands which are run. cheers! mar77i

Re: [dev] dmenu and dwm: is exec really needed

2016-04-28 Thread Martti Kühne
To allow for shell expressions is a neat thing, and if you don't need them, I can provide you with a patch. I did look into this topic another time, actually. I think I had modified dmenu_run to use exec in some way on one of my installations, but I appear to have currently misplaced it. cheers! m

Re: [dev] dmenu and dwm: is exec really needed

2016-04-28 Thread Mattias Andrée
On Thu, 28 Apr 2016 18:01:46 -0400 Greg Reagle wrote: > I use dwm. Sometimes I use Mod-p to start a GUI program > like firefox. I looked at the output of ps xf and noticed > that my shell is sticking around: > 21347 ?S 0:00 /usr/bin/fish > 21388 ?Rl 0:04 \_ iceweasel >

[dev] dmenu and dwm: is exec really needed

2016-04-28 Thread Greg Reagle
I use dwm. Sometimes I use Mod-p to start a GUI program like firefox. I looked at the output of ps xf and noticed that my shell is sticking around: 21347 ?S 0:00 /usr/bin/fish 21388 ?Rl 0:04 \_ iceweasel I can type `exec firefox` instead of `firefox` to avoid this, bu