From: David Kastrup <dak@gnu.org>
Cc: Luc Teirlinck <teirllm@dms.auburn.edu>,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: library-specific customization files?
Date: Sun, 31 Oct 2004 08:39:26 +0100 [thread overview]
Message-ID: <x5y8hn5ob5.fsf@lola.goethe.zz> (raw)
In-Reply-To: <FDELKNEBLPKKDCEBEJCBIEAKCJAA.drew.adams@oracle.com> (Drew Adams's message of "Sat, 30 Oct 2004 19:52:50 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> Thanks for this reference. I took a quick look at it.
>
> John's code tries to match against variable names. I think it would be good
> to build on what he has done, integrating it within Customize.
>
> Name matching is not 100% failsafe, since not all variable names in all Lisp
> packages use prefixes, and some name parts could also, I imagine, result in
> false hits to the wrong library.
>
> Instead of relying on name matching, Customize should use positive
> knowledge of which variables belong to which Lisp files to create a
> failsafe mapping. A library census a la TAGS could be used, if
> Customize does not already have an explicit mapping of variables to
> their libraries.
Customization variables already have groups. But I don't see how
splitting them makes any sense: the stuff that customize writes is not
supposed to be user-accessible anyway.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2004-10-31 7:39 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x5y8hn5ob5.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=teirllm@dms.auburn.edu \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).