Re: app-defaults vs. Xresources
The Xresources file will get read by every program and kept in its
database, whether or not the Xresources items are relevant to that
program. The xdvi specific information is kept in xterm and referred
to whenever the database is referenced. You are right--separating
configuration and code is good. That is why applications defaults
files were created.
Winfried Truemper <firstname.lastname@example.org> writes:
> On 11 Jan 1997, Kevin Dalley wrote:
> > It is inefficient to have application-specific defaults in every
> > program's database.
> It's not the program's database. It's the program's defaults file.
> It could have also compiled into the executable but then it would have
> been more difficult to look at the defaults and to use them in
> If you think this is inefficient, you are right but this bug is a feature.
> Seperating configuration and code _always_ has some overhead, but the
> advantages weigh more.
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com