From: Kim-Minh Kaplan <kmkaplan@vocatex.fr>
Subject: Re: problem with picons
Date: 16 Nov 1999 12:00:33 +0100 [thread overview]
Message-ID: <87iu323dm6.fsf@kloug.western.fr> (raw)
In-Reply-To: <87hfio3tiq.fsf@majikthise.adsl.duke.edu>
Dan Mills writes:
> The problem is that it doesn't display any picons at all. I tried
> going with the "Easy Picons" solution from the manual, but Gnus
> complained that gnus-picons-display-where was nil
That's strange: it is supposed to default to 'picons. Can you check
that you don't set it in one of your init files. And also check thaht
you can browse the picon URL (M-x w3-fetch RET
http://www.cs.indiana.edu:800/piconsearch RET).
Kim-Minh.
next prev parent reply other threads:[~1999-11-16 11:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-15 11:04 Dan Mills
1999-11-16 11:00 ` Kim-Minh Kaplan [this message]
1999-11-16 6:22 ` Dan Mills
1999-11-16 14:48 ` Kim-Minh Kaplan
1999-11-16 22:22 ` David Porter
1999-11-17 13:59 ` Dan Mills
1999-11-17 16:14 ` Dan Mills
1999-11-18 10:30 ` Kim-Minh Kaplan
1999-11-18 17:54 ` Dan Mills
1999-11-19 21:35 ` Matt McClure
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=87iu323dm6.fsf@kloug.western.fr \
--to=kmkaplan@vocatex.fr \
/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).