Bug#456109: xscreensaver: Please write only non-default settings

2012-07-18 Thread Jamie Zawinski
There is no way to make anything work sensibly for typical users without overwriting the whole file. The morass of places that one can set X resources, some of which haven't been commonly used for decades but that still work, makes this problem intractable. The X configuration mechanism is

Bug#456109: xscreensaver: Please write only non-default settings

2012-07-11 Thread Ian Zimmerman
Your wishes do not correspond with reality. Sorry. Not a bug. I don't understand. Doesn't a bug by definition conflict with reality? I too find this behavior of xscreensaver extremely annoying; partly because the explanation of the various timeout options in the manpage is barely

Bug#456109: xscreensaver: Please write only non-default settings

2007-12-13 Thread Jamie Zawinski
I'd like to keep my xscreensaver settings in Git, which I currently do for many other dotfiles. I want that configuration to contain a very minimal set of settings, to just blank and lock: Your wishes do not correspond with reality. Sorry. Not a bug. -- To UNSUBSCRIBE, email to [EMAIL

Bug#456109: xscreensaver: Please write only non-default settings

2007-12-12 Thread Josh Triplett
Package: xscreensaver Version: 5.04-1 Severity: wishlist I'd like to keep my xscreensaver settings in Git, which I currently do for many other dotfiles. I want that configuration to contain a very minimal set of settings, to just blank and lock: timeout:0:10:00 lock: True