From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lennart Borgman'" <lennart.borgman@gmail.com>
Cc: 'Emacs-Devel devel' <emacs-devel@gnu.org>
Subject: RE: autoload cookies for defcustoms
Date: Sat, 23 Jan 2010 12:38:45 -0800 [thread overview]
Message-ID: <138D93716A5443438E180B7C960F0A63@us.oracle.com> (raw)
In-Reply-To: <e01d8a51001231224s12f3a652y32b439ce842526db@mail.gmail.com>
> > Is there a policy, for the Lisp code distributed with
> > Emacs, about using autoload cookies for defcustoms?
> > If so, what is it?
>
> We had a discussion about that in November:
> http://lists.gnu.org/archive/html/emacs-devel/2009-11/msg00504.html
>
> The conclusion there was that all defcustoms (~7000) can't be
> autoloaded but that we can probably set it up so that completion of
> options knows all option names (and maybe apropos can know about them
> too).
Yes, but even though that is somewhat related, it does not address the questions
I raised. In particular (but not only): what is the current policy about when to
add an autoload cookie?
> But we did not finish that. I think I have some more things to test
> there, but anyone who want to join is of course wellcome.
That is a different topic. My questions are about the current autoload-cookie
policy.
next prev parent reply other threads:[~2010-01-23 20:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 18:31 autoload cookies for defcustoms Drew Adams
2010-01-23 20:24 ` Lennart Borgman
2010-01-23 20:38 ` Drew Adams [this message]
2010-01-25 2:56 ` Stefan Monnier
2010-01-25 5:13 ` Drew Adams
2010-01-25 15:31 ` Stefan Monnier
2010-01-25 20:36 ` Drew Adams
2010-01-26 2:05 ` Stefan Monnier
2010-01-26 3:12 ` Drew Adams
2010-01-26 11:51 ` Juanma Barranquero
2010-08-29 9:46 ` Wojciech Meyer
2010-08-29 19:11 ` Glenn Morris
2010-08-30 12:30 ` Wojciech Meyer
2010-08-30 15:54 ` Stefan Monnier
2010-08-30 23:20 ` Glenn Morris
2010-08-30 23:52 ` Wojciech Meyer
2010-08-31 3:32 ` Andy Wingo
2010-08-31 8:04 ` Stefan Monnier
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=138D93716A5443438E180B7C960F0A63@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
/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.