The previous logic leaves a shell running for the duration that the
launched application runs.
This changes it so that the only application that is left running is
the launched application.
In addition, it can now handle launching applications with spaces in
the filename.
---
dmenu_run | 2 +-
1
2013/4/16 Ross Lagerwall rosslagerw...@gmail.com:
The previous logic leaves a shell running for the duration that the
launched application runs.
This changes it so that the only application that is left running is
the launched application.
In addition, it can now handle launching
On Tue, Apr 16, 2013 at 01:35:44PM +0400, Alexander Sedov wrote:
2013/4/16 Ross Lagerwall rosslagerw...@gmail.com:
The previous logic leaves a shell running for the duration that the
launched application runs.
This changes it so that the only application that is left running is
the
2013/4/16 Ross Lagerwall rosslagerw...@gmail.com:
How did it handle command-line arguments before?
Command-line arguments are passed to dmenu as before.
Running dmenu_run -b would pass the -b to dmenu.
AFAICT, the pipeline outputs an executable with no other arguments.
I mean, previously I
On Tue, Apr 16, 2013 at 04:15:16PM +0400, Alexander Sedov wrote:
2013/4/16 Ross Lagerwall rosslagerw...@gmail.com:
How did it handle command-line arguments before?
Command-line arguments are passed to dmenu as before.
Running dmenu_run -b would pass the -b to dmenu.
AFAICT, the pipeline
On 2013-04-16, at 10:17, Ross Lagerwall wrote:
-dmenu_path | dmenu $@ | ${SHELL:-/bin/sh}
+exec $(dmenu_path | dmenu $@)
On 2013-04-16, at 15:47, Ross Lagerwall wrote:
-dmenu_path | dmenu $@ | ${SHELL:-/bin/sh}
+eval exec $(dmenu_path | dmenu $@)
To not screw up the argument passing, you
