On Mon, Sep 24, 2007 at 08:50:53PM +0100, Chris Webb wrote:
> "Anselm R. Garbe" <arg_AT_suckless.org> writes:
>
> > it won't last long that the need arises to also configure the key
> > bindings, and the terminal command, and the dmenu command, and what not
> > using such capabilities.
>
> Actually... :-)
>
> What wasn't in that patch, but is in my tree, is a little convenience
> function that lets you define commands by name in .Xresources:
>
> Dwm.command.xterm: urxvt -bg red
> Dwm.command.browser: opera
>
> and then bind them in config.h
>
> Key keys[] = {
> [...]
> { MODKEY, XK_Return, spawn_command, "xterm" }
> { MODKEY | ShiftMask, XK_Return, spawn_command, "browser" }
> [...]
> }
I don't see much benefit in this design, because you have to
edit config.h anyways. And in my opinion key bindings don't
change frequently, same with appearance stuff. Hell, if
dwm configuration is such an issue, what's the problem in
extracting the dwm tarball to $HOME/.dwm and writing a dwm
wrapper script instead which calls make before starting dwm?
So you can configure dwm easily through editing
$HOME/.dwm/config.h, and you won't notice a big difference (X
usually takes longer to start up than dwm to compile)...
Regards,
-- Anselm R. Garbe >< http://www.suckless.org/ >< GPG key: 0D73F361Received on Tue Sep 25 2007 - 08:04:54 UTC
This archive was generated by hypermail 2.2.0 : Sun Jul 13 2008 - 14:55:26 UTC