From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: [gnu.emacs.gnus] Re: [Gnus-FAQ] Draft 2
Date: Sat, 11 Jan 2003 21:38:50 +0100 [thread overview]
Message-ID: <m3of6nzajp.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <843co1grky.fsf@lucy.cs.uni-dortmund.de>
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> The problem of undefined variables happens often. Hm. Does it make
> sense to put an autoload marker on the variable?
Yes, I think so... I'm not 100% sure, though.
> What criteria do Emacs developers use to decide whether to mark a
> variable to autoload?
I guess if it's usual to alter the variable before you load the
package, then it should be autoloayded. I'm not sure why the user
here isn't just setting the variable instead of using `add-to-list'
and the like.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2003-01-11 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 23:07 Frank Schmitt
2003-01-10 11:41 ` Kai Großjohann
2003-01-11 20:38 ` Lars Magne Ingebrigtsen [this message]
2003-01-12 14:15 ` Kai Großjohann
2003-01-12 14:18 ` Lars Magne 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3of6nzajp.fsf@quimbies.gnus.org \
--to=larsi@gnus.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.
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 NNTP newsgroup(s).