On Sat, 27 Feb 2010, Nicolas Bonifas wrote: > > in order to make anyone using the stock default of any of these items > > swear and curse loud at the next upgrade? > > I think that what Juan Francisco suggests is to change the defaults for new > installations. It would not change anything for current users, even on > upgrade, since the parameters would still be read from the stored > configuration files.
are you sure one's saved configuration includes _all_ configuration items? at 132 lines (many items being mult-line) my ~/G/D/WindowMaker looks quite thin to include all of them. that pretty much means that the rest is taken from some kind of a default. presto behaviour change, at (almost) every item. take for example DontLinkWorkspaces. i do not have it turned on (no ws switching when dragging windows against the screen edge). i do not have it not turned on by having "DontLinkWorkspaces = no" in ~/G/D/WindowMaker or anywhere under ~/G, but i have it not turned on via it being turned off is a default. now, the next windowmaker, implementing the suggested change, comes out, and since i do not explicitly have it turned off, *due to a behaviour change*, it will get turned on. sure-fire way to make all my colleagues run and duck for cover the first time i hit this ;) > My opinion is that although most of Juan Francisco's proposed changes suit > more my needs than the current defaults, most (if not all) Window Maker users > already have a personalized configuration, so changing the default values or > not is not a big issue. had every and all configuration item gotten saved by wprefs (or wmakerconf even, i'm making some compromise here), it wouldn't be a big issue, but i am very strongly against it implementing like this. such a change should be implemented over several releases, with stages like now+1 wprefs saves all configuration, now+2 something i didn't think of, now+3 some other thing i didn't think of but others have, now+4 makes the changes in the default. -- [-] mkdir /nonexistent -- To unsubscribe, send mail to [email protected].
