On 11 November 2010 23:59, TJ Robotham <tj.robotham_AT_gmail.com> wrote:
> Meh, I can't really think of a particularly compelling reason to put config.h
> back in, but from the perspective of someone who was using it, its removal
> feels strange and arbitrary and a bit like someone insisting that I get out of
> bed at some early hour on a weekend.
A lot of people just use the dmenu prebuilt binary anyway, and their
window manager (like dwm) uses the flags to configure. I remember when
I first pulled dwm and dmenu I was very confused by how changing
dmenu/config.h had no effect on dwm's Alt-p. Maybe that was just me,
but distributing config.def.h as the default defaults seems a bit
crazy. dmenu-4.2 (when it does release) will be a pretty major update,
so it's like how dwm-5.0's config.h was completely different to 4.9's.
:p
On 12 November 2010 00:12, Peter John Hartman
<peterjohnhartman_AT_gmail.com> wrote:
> 1. At the moment, keybindings are defined in dmenu.c and so if one wants
> to change keybindings, then one has to fiddle with that. All other suckless
> apps put the keybindings in config.h (afaik).
>
> 2. Future config options that don't fit easily as arguments would also go in
> config.h. Depending on how this filter thing filters out (ha. ha.) it could
> also plausibly go there.
Only dwm, surf, tabbed, as far as I'm aware. There is the possibility
of a patch allowing the control codes to be overridden, but having
looked at the code again I'm not sure how to do this in a particularly
user-friendly way without considerably bloating the source. Likewise
modes. I mean, how do we know which bits people want to configure?
It's not obvious like with dwm's layouts, as there is no single point
of interest (I bet most dmenu patches don't overlap).
cls
Received on Fri Nov 12 2010 - 01:23:45 CET
This archive was generated by hypermail 2.2.0 : Fri Nov 12 2010 - 01:36:01 CET