From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: gnus-picons-database vs. gnus-picon-databases
Date: Sun, 20 Jan 2002 00:02:40 +0100 [thread overview]
Message-ID: <m3g052lzan.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <k8zbsfwyhu8.fsf@alcatel.de>
Colin Marquardt <c.marquardt@alcatel.de> writes:
> my gnus.texi from a week ago seems to always document the variable
> gnus-picons-database, while the code in gnus-picon.el uses
> gnus-picon-databases. No patch as it's so easy to fix...
>
> Also, does the statement
>
> | * Picon Requirements:: Don't go further if you aren't using XEmacs.
>
> still hold true?
No. The entire section on picons in the manual will be ripped out and
replaced by something that actually documents how the picons code
works now, but I'm not quite sure I'm happy with how it works now, so
I've put off doing something about it. Real Soon Now.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2002-01-19 23:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 17:15 Colin Marquardt
2002-01-19 23:02 ` 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=m3g052lzan.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).