From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 11106@debbugs.gnu.org
Subject: bug#11106: 24.0.94; enhancement request: have autoload treat faces like it does options
Date: Wed, 28 Mar 2012 11:50:48 -0400 [thread overview]
Message-ID: <jwvsjgsbuhu.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <A80D77484F90482182EB378D7E9E6551@us.oracle.com> (Drew Adams's message of "Wed, 28 Mar 2012 06:39:39 -0700")
> For #1: Make an autoload cookie before a defface do something
> analogous to what it does before a defcustom. I'm no expert on the
> latter, so yes, this is vague. IIUC, an autoload cookie handles an
> option definition by setting the option value at autoload time, but it
> does not simply copy the defcustom to the autoloads file.
;;;###autoload on a defcustom pretty much copies the defcustom, tho it
addmittedly tries to strip away things that won't be needed until the
file is actually loaded.
But I don't know what that would mean for defface. IOW what is the
concrete problem you see with ;;;###autoload on a defface that you'd
like to see fixed?
> Assume you want to provide autoloading for the faces,
I can't assume it, since you're trying to explain to me why that would
be useful.
> to let users get to their doc.
That's it? So you only want it for describe-face's purpose?
Then autoloading is not the right answer. We're back at the issue of
finding documentation for vars, functions, and now faces in not-yet
loaded code. We don't need to autoload the whole world for that.
[ Sorry, didn't read the rest, assuming that it is not relevant since
I rejected the main assumption. ]
Stefan
next prev parent reply other threads:[~2012-03-28 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 23:57 bug#11106: 24.0.94; enhancement request: have autoload treat faces like it does options Drew Adams
2012-03-28 0:31 ` Drew Adams
2012-03-28 12:41 ` Stefan Monnier
2012-03-28 13:39 ` Drew Adams
2012-03-28 15:50 ` Stefan Monnier [this message]
2012-03-28 17:08 ` Drew Adams
2012-03-28 18:45 ` Stefan Monnier
2016-04-28 14:17 ` Lars Ingebrigtsen
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=jwvsjgsbuhu.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=11106@debbugs.gnu.org \
--cc=drew.adams@oracle.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 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).