Re: X config not written
- To: debian-user@lists.debian.org
- Subject: Re: X config not written
- From: Andreas Janssen <andreas.janssen@bigfoot.com>
- Date: Tue, 01 Mar 2005 11:28:01 +0100
- Message-id: <[🔎] d01for$bsr$1@sea.gmane.org>
- References: <3Cu0i-5uY-5@gated-at.bofh.it> <3Cv61-6lP-13@gated-at.bofh.it> <3CwY9-7Sx-13@gated-at.bofh.it> <3Cxhv-8eB-7@gated-at.bofh.it> <4221D8C9.3070804@my.home> <20050227220027.GA1681@nitpicking.com> <cvvho3$v1v$1@sea.gmane.org> <cvvpuu$ti1$1@sea.gmane.org> <20050301012720.GA29438@nitpicking.com>
Hello
Carl Fink (<carlf@fink.to>) wrote:
> On Mon, Feb 28, 2005 at 08:09:32PM +0100, Andreas Janssen wrote:
>> This behaviour is documented in the configuration file itself, and
>> in the Debian X FAQ.
>
> So? Since it's documented in a file the user isn't looking at, it
> can't be explained by the program right when the user needs to know
> it? You think it's GOOD to force people to do research every time
> they run apt-get update?
I agree that a warning could be helpful, but I also think that the
maintainers can expect people to /read/ the configuration file when
they want to edit it.
best regards
Andreas Janssen
--
Andreas Janssen <andreas.janssen@bigfoot.com>
PGP-Key-ID: 0xDC801674 ICQ #17079270
Registered Linux User #267976
http://www.andreas-janssen.de/debian-tipps-sarge.html
Reply to: