From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: drafts
Date: Sun, 7 May 2000 18:15:58 +0200 [thread overview]
Message-ID: <200005071615.SAA06286@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Clinton Roy's message of "07 May 2000 23:01:09 +1000"
Clinton Roy <latte@uq.net.au> writes:
> 2) Getting that header information into the summary line is a
> pain. Why isn't there a format spec for the To header? Why the
> complex two-in-one spec and another regexp?
This was intended to be used in other groups, as well. For messages
sent by others, the author name is shown, for messages from you, `->'
is shown plus the recipient's name.
Hm. I think the drafts group is a special case. Maybe it would be
nice to have an additional spec which always shows the To header...
kai
--
Beware of flying birch trees.
next prev parent reply other threads:[~2000-05-07 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-11 13:15 drafts Clinton Roy
2000-03-11 15:26 ` drafts Karl Kleinpaste
2000-03-14 18:15 ` drafts Christoph Rohland
2000-03-14 20:12 ` drafts Karl Kleinpaste
2000-05-07 13:01 ` drafts Clinton Roy
2000-05-07 14:11 ` drafts Karl Kleinpaste
2000-05-07 16:15 ` Kai Großjohann [this message]
2000-05-08 2:16 ` drafts Clinton Roy
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=200005071615.SAA06286@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).