Dear Tyler, On Fri, 17-01-2014, at 04:41, tyler@plantarum.ca wrote:

Hello,

A few notes about the problem I described below. I referred to tab completion in xmobar - of course I should have said dmenu. The problem (dmenu lacking tab completion of any sort) persists, even after completely purging all xmonad and haskell packages from Debian and reinstalling. A similar problem is described here: https://www.linuxquestions.org/questions/slackware-14/dmenu-4175435436/

From the forum post, the problem was resolved, but without any clear suggestions as to how or why. Does anyone have any suggestions on how to fix this?

How are you calling dmenu? I think you might need to use "dmenu_run", NOT just "dmenu" (and this is something that changed sometime in the past). This is what I have now in my xmonad.hs , ((modMask, xK_p ), spawn "dmenu_run") If you change your xmonad.hs you will need to do xmonad --recompile xmonad --restart (That said, I find dmenu is sometimes too slow, and I end up using gmrun and typing the command and completing in there). Best, R.

Thanks,

Tyler

On 10/01/14 06:44 PM, Tyler Smith wrote:

...

Hello,

I have been using xmonad for a few weeks. After updating via aptitude on Debian unstable a few days ago, xmobarno longer offers tab-completions. It still works, but I have to ype out the whole command name. The colour of the bar is now black as well.

I found some discussion of this on a forum. A solution was to rebuild xmonad. Not knowing Haskell, I'm not sure how to do this.

Is there another solution? If not, how do I rebuild xmonad - is this even possible with the Debian package, or do I need to install from source?

_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad

-- Ramon Diaz-Uriarte Department of Biochemistry, Lab B-25 Facultad de Medicina Universidad Autónoma de Madrid Arzobispo Morcillo, 4 28029 Madrid Spain Phone: +34-91-497-2412 Email: rdiaz02@gmail.com ramon.diaz@iib.uam.es http://ligarto.org/rdiaz

On Fri, Jan 17, 2014 at 8:17 AM, Tyler Smith wrote:

I switched from:

, ((modm, xK_p ), spawn "exe=`dmenu_path | dmenu` && eval \"exec $exe\"")

to

, ((modm, xK_p ), spawn "dmenu_run")

and dmenu is now working again.

I infer that you have one of those "build up the default from scratch" configs. We have a comment in that example config saying "don't use this as a real config", but various Linux distributions like to remove that comment and recommend its use. If you had not used it, xmonad would probably have handled the dmenu change for you with at most an "xmonad --recompile" needed. This is *why* we disrecommend use of that config --- it hides any changes we make later to xmonad to adapt to changing external utilities, and can hide new functionality. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net

That is exactly my situation; I've been using xmonad for about 4 years, but know no haskell. So early on I created my ~/.xmonad/xmonad.hs, and started cutting and pasting from online examples to change key bindings, etc. R. On Sun, 19-01-2014, at 17:15, tyler@plantarum.ca wrote:

Thanks, that's good to know.

As a newbie, it's very confusing trying to get a basic config set up. There are numerous conflicting examples online. I think I used this one, from the xmonad wiki:

http://www.haskell.org/haskellwiki/Xmonad/Config_archive/Template_xmonad.hs_...)

It includes the problematic dmenu line. If I'm meant to infer from the comments in that file that it's not suitable as a base xminad.hs, it's not clear to me. There is a line indicating 'normally you'd only override the defaults you're interested in' - which I interpreted as meaning use the file verbatim, and change only lines that you need to. Which is what I did. Perhaps the wording could be clarified?

Part of my problem is that Haskell doesn't resemble any language I'm familiar with, so for now anything more involved than changing a key binding requires cutting and pasting from online examples.

Thanks,

Tyler

Brandon Allbery wrote:

...

On Fri, Jan 17, 2014 at 8:17 AM, Tyler Smith wrote:

...

I switched from:

, ((modm, xK_p ), spawn "exe=`dmenu_path | dmenu` && eval \"exec $exe\"")

to

, ((modm, xK_p ), spawn "dmenu_run")

and dmenu is now working again.

I infer that you have one of those "build up the default from scratch" configs. We have a comment in that example config saying "don't use this as a real config", but various Linux distributions like to remove that comment and recommend its use.

If you had not used it, xmonad would probably have handled the dmenu change for you with at most an "xmonad --recompile" needed. This is *why* we disrecommend use of that config --- it hides any changes we make later to xmonad to adapt to changing external utilities, and can hide new functionality.

-- Ramon Diaz-Uriarte Department of Biochemistry, Lab B-25 Facultad de Medicina Universidad Autónoma de Madrid Arzobispo Morcillo, 4 28029 Madrid Spain Phone: +34-91-497-2412 Email: rdiaz02@gmail.com ramon.diaz@iib.uam.es http://ligarto.org/rdiaz