dmenu update changes behaviour

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Update dmenu to 20110719
2. Using default config, press <mod>p

What is the expected output? What do you see instead?
Expected: dmenu to run as before
Actual: dmenu runs, but no choices, like ``dmenu < /dev/null''

What version of the product are you using? On what operating system?
xmonad 0.9.2

Please provide any additional information below.

Fix by using ``spawn "dmenu_run" '' instead of ``spawn "exe=`dmenu_path | 
dmenu` && eval \"exec $exe\"" '' in default config file.

Original issue reported on code.google.com by bjmpr...@gmail.com on 24 Jul 2011 at 10:02

GoogleCodeExporter commented 9 years ago

Hrm. This is a difficult decision. It seems as though dmenu_path was removed 
and replaced with lsx instead. Updating XMonad will break compatability with 
previous versions. Should the minimum required dmenu be bumped?

(20110719 is 4.4 btw)

Original comment by MathStuf@gmail.com on 25 Jul 2011 at 11:58

GoogleCodeExporter commented 9 years ago

Can we check for lsx and use dmenu_path as appropriate? Something like

spawn "which lsx && dmenu_run || (exe=`dmenu_path | dmenu` && eval \"exec 
$exe\")"

?

Original comment by daniel.w...@gmail.com on 26 Jul 2011 at 1:19

GoogleCodeExporter commented 9 years ago

lsx used to be separate, but is now part of dmenu, so it's not a good 
indicator. dmenu_run probably is, however.

Original comment by MathStuf@gmail.com on 26 Jul 2011 at 1:39

rlopez1j / xmonad

dmenu update changes behaviour #467