From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Picons - still not quite right.
Date: Tue, 01 Jan 2002 14:39:14 +0100 [thread overview]
Message-ID: <m3n0zyw5q5.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <microsoft-free.x4d70u5hx0.fsf@slackware.mynet.pc>
Steve Youngs <youngs@xemacs.org> writes:
> 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.
Might be a header parsing problem again. I think I'll alter the code
not to use `mail-header-parse-addresses'.
> Betcha wishing you hadn't decided to rewrite the picon code, huh? :-P
Je ne regrette rien!
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2002-01-01 13:39 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
2002-01-01 13:38 ` Steve Youngs
2002-01-01 13:39 ` Lars Magne Ingebrigtsen [this message]
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=m3n0zyw5q5.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).