From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Gnus 5.2.20: SAVEDIR
Date: 21 Jun 1996 08:53:47 +0200 [thread overview]
Message-ID: <x6afxxodfo.fsf@eyesore.no> (raw)
In-Reply-To: Mark Borges's message of 20 Jun 1996 10:56:55 -0600
Mark Borges <mdb@cdc.noaa.gov> writes:
> Is it safe to assume that all valid variables in Gnus-5.2.20 are
> documented?
Yes, just about.
> I'd go ahead and just do it, but I see stuff like
>
> $ grep gnus-use-generic-from *.el
> gnus.el:(defvar gnus-use-generic-from nil)
> $
>
> which I don't understand -- why is it defvar'd and never used?
It's a variable from GNUS 4.1 left in for people who rely on it being
defined.
--
"Yes. The journey through the human heart
would have to wait until some other time."
prev parent reply other threads:[~1996-06-21 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199606200515.XAA10443@gielgud.lanl.gov.xdiv>
1996-06-20 6:22 ` Mark Borges
1996-06-20 14:18 ` John Turner
1996-06-20 14:47 ` Lars Magne Ingebrigtsen
1996-06-20 16:56 ` Mark Borges
1996-06-21 6:53 ` Lars Magne Ingebrigtsen [this message]
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=x6afxxodfo.fsf@eyesore.no \
--to=larsi@ifi.uio.no \
/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).