all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Lennart Borgman" <lennart.borgman.073@student.lu.se>
Subject: Re: library-specific customization files?
Date: Sat, 30 Oct 2004 23:03:18 +0200	[thread overview]
Message-ID: <075401c4bec9$5ecb1d10$0200a8c0@sedrcw11488> (raw)
In-Reply-To: MEEKKIABFKKDFJMPIOEBCEGCCHAA.drew.adams@oracle.com

----- Original Message ----- 
From: "Drew Adams" <drew.adams@oracle.com>

...
: I think that multiple customization files, each associated with a standard
: library file, could make it easier for users to keep track of things, and
: easier for them to adapt to new Emacs versions. Making this optional would
: be important, because for some users this might be more confusing than
: helpful.

I agree, this would be a nice feature. I did not give it a thourogh thought
but would it not be possible to use the :group attribute for this? Maybe the
group names could be tied to file names for saving? It no such association
then the main customization file could maybe be used?

Some people might perhaps be confused by the group "hierarchy" here. Is not
this more a network than a hierarchy? Could the feature suggested above be
kept outside of this?

- Lennart

  reply	other threads:[~2004-10-30 21:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-30 18:50 library-specific customization files? Drew Adams
2004-10-30 21:03 ` Lennart Borgman [this message]
2004-11-01  7:23   ` Richard Stallman
2004-10-31  0:16 ` Stefan
2004-10-31  0:50   ` Luc Teirlinck
2004-10-31  1:02     ` Drew Adams
2004-10-31  2:52       ` Drew Adams
2004-10-31  7:39         ` David Kastrup
2004-10-31  9:15           ` Lennart Borgman
2004-10-31  9:18             ` David Kastrup
2004-10-31 17:03               ` Lennart Borgman
2004-10-31 17:01             ` Stefan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='075401c4bec9$5ecb1d10$0200a8c0@sedrcw11488' \
    --to=lennart.borgman.073@student.lu.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.