You are not logged in.
Pages: 1
dmenu 4.4 has dropped dmenu_path in favor of lsx.
I was using
((modm, xK_p ), spawn "exe=`dmenu_path | yeganesh` && eval \"exec $exe\"")
to launch yeganesh from Xmonad.
I'm trying to use lsx instead of the now absent dmenu_path without success. For now I'm using dmenu-path-c.
Has anyone managed to use lsx with yeganesh ?
Cedric Girard
Offline
`man lsx'
This silver ladybug at line 28...
Offline
Thanks. I haven't thought of looking at the man page!
What I don't know exactly is what was the behavior of dmenu_path. Was it updating a cache (when ?) and returning its content ? In that case lsx alone will be more disk intensive.
An other thing I don't understand: "lsx $PATH" does not work but it seems to be used by dmenu_run that way !
I succeeded to use lsx that way "echo $PATH | sed 's!:! !g' | xargs lsx | yeganesh" . But this is neither elegant nor optimal.
Cedric Girard
Offline
What I don't know exactly is what was the behavior of dmenu_path. Was it updating a cache (when ?) and returning its content ? In that case lsx alone will be more disk intensive.
I don't know what dmenu_path did, but dmenu_run maintains a cache.
An other thing I don't understand: "lsx $PATH" does not work but it seems to be used by dmenu_run that way !
dmenu_run simply calls `lsx $PATH' since it sets IFS to `:'. See bash(1).
You should either just use dmenu_run, or modify dmenu_run to use yeganesh (although I don't know what it is) and use the modified script instead.
This silver ladybug at line 28...
Offline
I didn't see the part about IFS. I should have thought about that.
Yes maybe, adapting dmenu_run should be the way.
Yeganesh is a wrapper to dmenu. It sorts results by frequency of usage. Thus you only need to type a few letter to launch the application you launch every day.
Cedric Girard
Offline
I succeeded to use lsx that way "echo $PATH | sed 's!:! !g' | xargs lsx | yeganesh" . But this is neither elegant nor optimal.
But it works, which is all I needed for the time being; thanks.
Offline
Pages: 1