From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: :file keyword for Customize
Date: Fri, 09 May 2008 09:01:17 -0500 [thread overview]
Message-ID: <86mymzpoeq.fsf@lifelogs.com> (raw)
In-Reply-To: 001501c8b152$46d778a0$0ab32382@us.oracle.com
On Thu, 8 May 2008 14:27:10 -0700 "Drew Adams" <drew.adams@oracle.com> wrote:
DA> What I was thinking was that library writers would typically provide
DA> one or more user options or functions as the :file sexps - it is
DA> those sexps that would then let users, in effect, determine the
DA> :file values used. IOW, end users would not directly determine the
DA> sexps used for :file, but they would ultimately determine the values
DA> of those sexps in some way (defined by the programmer).
...
DA> In what I imagine, programmers can do that as they like, using
DA> whatever code they think is appropriate as the various :file
DA> sexps. [...] They can do just about anything they think is
DA> appropriate for their users.
That seems really complicated, and still requires every package to do it
explicitly.
It seems like you're trying to set up a :filegroup option, really, which
tells the Customize interface that some options should be logically
grouped together when they are saved. I think defgroup does this
logical grouping already for the vast majority of options, so it's a
matter of saying "save this defgroup's variables in file X." That may
be possible as an optional add-on package that doesn't change the way
Customize works normally. The approach you proposed would, I think,
require changes to the core Customize behavior instead so it's less
desirable.
Ted
next prev parent reply other threads:[~2008-05-09 14:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 16:35 :file keyword for Customize Drew Adams
2008-05-08 16:43 ` Jason Rumney
2008-05-08 16:59 ` Drew Adams
2008-05-08 17:08 ` Jason Rumney
2008-05-08 17:41 ` Ted Zlatanov
2008-05-08 18:00 ` Drew Adams
2008-05-08 19:12 ` Ted Zlatanov
2008-05-08 21:27 ` Drew Adams
2008-05-09 14:01 ` Ted Zlatanov [this message]
2008-05-08 20:00 ` Stephen J. Turnbull
2008-05-08 21:27 ` Drew Adams
2008-05-08 21:34 ` Jason Rumney
2008-05-09 6:43 ` Stephen J. Turnbull
2008-05-09 8:37 ` Bastien
2008-05-08 18:00 ` Drew Adams
2008-05-08 20:48 ` David Kastrup
2008-05-08 21:34 ` Drew Adams
2008-05-08 21:48 ` Jason Rumney
2008-05-08 22:10 ` Drew Adams
2008-05-08 22:31 ` David Kastrup
2008-05-08 21:51 ` David Kastrup
2008-05-09 14:11 ` Ted Zlatanov
2008-05-09 14:34 ` David Kastrup
2008-05-09 15:07 ` Ted Zlatanov
2008-05-09 21:17 ` Stephen J. Turnbull
2008-05-12 13:13 ` :password customize type (was: :file keyword for Customize) Ted Zlatanov
2008-05-09 11:12 ` :file keyword for Customize Richard M Stallman
2008-05-13 13:53 ` Paul R
2008-05-13 14:28 ` Stefan Monnier
2008-05-13 21:48 ` Miles Bader
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=86mymzpoeq.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.org \
/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).