From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: Per Abrahamsen <abraham@dina.kvl.dk>, ding@gnus.org
Subject: Re: integrating x-face stuff
Date: 13 Jan 2001 00:31:20 +0100 [thread overview]
Message-ID: <vaf7l40uz3r.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m37l40qthq.fsf@h0050bad6338d.ne.mediaone.net>
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.
There have been previous attempts (well, at least one) to improve the
Gnus documentation so that people realize that they should look in the
Message info file, instead.
Alas, this does not appear to have been sufficient.
If you told us where in the Gnus info file you looked, that might help
us to add more pointers to the Message info file in all the right
places.
Hm.
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
--
Be indiscrete. Do it continuously.
next prev parent reply other threads:[~2001-01-12 23:31 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 [this message]
2001-01-13 12:29 ` Nick Papadonis
[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=vaf7l40uz3r.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).