[xmonad] dmenu tab completion

[Tyler Smith]

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_(0.9)

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 <allbery.b at gmail.com> wrote:
>On Fri, Jan 17, 2014 at 8:17 AM, Tyler Smith <tyler at plantarum.ca>
>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.