From: Steve Youngs <youngs@xemacs.org>
Subject: Re: Picons - still not quite right.
Date: Tue, 01 Jan 2002 23:18:03 +1000 [thread overview]
Message-ID: <microsoft-free.x4d70u5hx0.fsf@slackware.mynet.pc> (raw)
In-Reply-To: <m3g05qxox2.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 01 Jan 2002 12:59:21 +0100")
|--==> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
LMI> Steve Youngs <youngs@xemacs.org> writes:
>>Note missing picon for "youngs".
LMI> Oh, right. But do you really want to have that "unknown" picon
LMI> displayed in 90% of all the messages?
The other side of the coin is why use picons at all if only 10% or
less of messages will have them?
If a picon exists that can be used, why not use it?
>>Also, if I don't set 'gnus-picon-databases' I don't see *any* picons.
>>In case you are wondering, my picons are in '/usr/local/faces/', one
>>of the default directories that Gnus is supposed to search in.
LMI> Yup. Fix in Oort Gnus v0.05 (i. e., CVS).
Yep, works.
Discovered something else though. :-( I'm now not seeing any picons
in Kai Großjohann's emails. Pretty sure that that used to work in the
updated gnus-picon.el, definitely in the old one.
Betcha wishing you hadn't decided to rewrite the picon code, huh? :-P
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs@xemacs.org>---|
next prev parent reply other threads:[~2002-01-01 13:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 11:34 Steve Youngs
2002-01-01 11:59 ` Lars Magne Ingebrigtsen
2002-01-01 12:35 ` Lars Magne Ingebrigtsen
2002-01-01 13:18 ` Steve Youngs [this message]
2002-01-01 13:38 ` Steve Youngs
2002-01-01 13:39 ` Lars Magne Ingebrigtsen
2002-01-01 14:07 ` Steve Youngs
2002-01-02 16:16 ` ShengHuo ZHU
2002-01-02 17:01 ` Steve Youngs
2002-01-02 19:35 ` ShengHuo ZHU
2002-01-02 20:55 ` Steve Youngs
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=microsoft-free.x4d70u5hx0.fsf@slackware.mynet.pc \
--to=youngs@xemacs.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).