On Mon, Mar 31, 2008 at 01:16:15PM -0400, gwern0@gmail.com wrote:
I don't like the idea of cluttering up XConfig with this sort of thing. I'd rather see the terminal pref removed (it seems silly for all the same reasons) than another pref (that's only used in contrib) added to the core of xmonad.
Well, that would be a second best. Consistency is a good thing here if we can't agree to my suggestion.
I would prefer both browser and terminal; they are both general interfaces, they are both universally used (heck, browser might be even more common - I could see many people not using terminals though they use browsers), and so on. The only other similarly used genres of programs are editors (covered by $EDITOR) and mail clients (are mail programs handled by env vars?). It's an easy two-line change at its most flagrant, and so on.
Actually, the browser is never be used in my xmonad.hs. In fact, it's only used by a very few contrib extensions.
If you prefer, we could alternately support XMONAD_BROWSER. Note that putting the browser in the environment would also make it immediately runtime-configurable (well, with a few lines of code in contrib).
See my other email about runtime-configurable; I think what would actually be runtime configurable is my suggestion (make it modifiable in xmonad.hs, not the shell configs).
Right, my approach would be configurable either in xmonad.hs or in the shell. -- David Roundy Department of Physics Oregon State University