Issue 467 in xmonad: dmenu update changes behaviour

Status: New Owner: ---- New issue 467 by bjmpr...@gmail.com: dmenu update changes behaviour http://code.google.com/p/xmonad/issues/detail?id=467 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.

Comment #1 on issue 467 by MathStuf: dmenu update changes behaviour http://code.google.com/p/xmonad/issues/detail?id=467 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)

Comment #2 on issue 467 by daniel.w...@gmail.com: dmenu update changes behaviour http://code.google.com/p/xmonad/issues/detail?id=467 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\")" ?

Comment #3 on issue 467 by MathStuf: dmenu update changes behaviour http://code.google.com/p/xmonad/issues/detail?id=467 lsx used to be separate, but is now part of dmenu, so it's not a good indicator. dmenu_run probably is, however.
participants (1)
-
codesite-noreply@google.com