From: Nick Papadonis <nick@coelacanth.com>
Cc: Per Abrahamsen <abraham@dina.kvl.dk>, ding@gnus.org
Subject: Re: integrating x-face stuff
Date: 13 Jan 2001 07:29:13 -0500 [thread overview]
Message-ID: <m3bstbd49y.fsf@h0050bad6338d.ne.mediaone.net> (raw)
In-Reply-To: <vaf7l40uz3r.fsf@lucy.cs.uni-dortmund.de>
>>>>> "Kai" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
> On 12 Jan 2001, Nick Papadonis wrote:
>> Yes, I did not know about message-default-headers. Excuse me
>> if I didn't read through every info file for each of X-Emacs's
>> lisp packages. I simply installed gnus, read all it's info
>> files, and was never pointed towards the message info file. I
>> don't know every internal working of gnus, nor should I have
>> to.
> The node `(gnus)Composing Messages' does point to the Message
> info file, but that might be too easily overlooked. Maybe it
> would be useful to include a sentence there which stands out
> more?
Kai,
The eye catcher for me was the picons section. I now realize that
PICONS are not the same as using the X-face: header. However there
are many (actually all) mentions of the work x-face in these
sections. It's what actually gave me some motivation of messing with
my headers. :)
For instance, 'If you want to display faces from `X-Face' headers, you
should have the `xface' support compiled into XEmacs. Otherwise you
must have the `netpbm' utilities installed, or munge the
`gnus-picons-convert-x-face' variable to use something else.'' What
if you want to add something like this in the header?
The sections that describe 'W f' - Look for and display any X-Face
headers. Maybe add something like: "If you want to add your own
x-face, add the header. See Message info file."
Just skimmed the composing messages section and a reference to the
Message info file didn't stand out. I would almost say mention in
posting styles, but that doesn't seem right?
What was the pointer to 'Message' in Composing Messages? I tried
looking for it...
- Nick
next prev parent reply other threads:[~2001-01-13 12:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 4:08 Nick Papadonis
2001-01-11 9:52 ` Per Abrahamsen
2001-01-11 10:02 ` Nick Papadonis
2001-01-11 11:28 ` Per Abrahamsen
2001-01-11 22:30 ` Nick Papadonis
2001-01-12 21:52 ` Kai Großjohann
2001-01-12 22:00 ` Kai Großjohann
2001-01-12 22:46 ` Nick Papadonis
2001-01-12 22:53 ` Charles Sebold
2001-01-12 23:13 ` Jack Twilley
2001-01-12 23:31 ` Kai Großjohann
2001-01-13 12:29 ` Nick Papadonis [this message]
[not found] ` <86ae8x5zf1.fsf@blowfish.brfmasthugget.se>
2001-01-12 11:50 ` Per Abrahamsen
2001-01-12 11:52 ` Per Abrahamsen
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=m3bstbd49y.fsf@h0050bad6338d.ne.mediaone.net \
--to=nick@coelacanth.com \
--cc=abraham@dina.kvl.dk \
--cc=ding@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).