From: Wesley.Hardaker@sphys.unil.ch
Cc: ding@ifi.uio.no
Subject: Re: picons problem
Date: 17 Jan 1997 08:19:31 +0100 [thread overview]
Message-ID: <qk27mlc93b0.fsf@iptsun2.unil.ch> (raw)
In-Reply-To: Andrew J Cosgriff's message of 17 Jan 1997 14:47:01 +1100
>>>>> "a" == Andrew J Cosgriff <ajc@bing.wattle.id.au> writes:
ajc> (this has been happening for ages, btw)
ajc> I have gnus-article-display-picons in my gnus-article-display-hook
ajc> (it's displaying in the article buffer)
ajc> Every article seems to display both text for the hostname and the
ajc> picons, but it's all mixed up, eg.
ajc> dsiu@adobe.[xpm for .com].[xpm for adobe].com
Hmm... I haven't heard anything like this from anyone really... The
question is, what exactly are you doing differently. Can you send me
the picons related stuff out of your .gnus file?
ajc> Presumably this isn't correct behaviour ?
Nope, it certainly isn't.
Wes
prev parent reply other threads:[~1997-01-17 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-17 3:47 Andrew J Cosgriff
1997-01-17 6:17 ` Danny Siu
1997-01-17 7:19 ` Wesley.Hardaker [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=qk27mlc93b0.fsf@iptsun2.unil.ch \
--to=wesley.hardaker@sphys.unil.ch \
--cc=ding@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).