From: Reiner Steib <reinersteib+gmane@imap.cc>
To: bugs@gnus.org
Cc: <ding@gnus.org>
Subject: Re: "From" not as good as it could be?
Date: Sun, 02 Dec 2007 00:32:15 +0100 [thread overview]
Message-ID: <v9d4tq3sao.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87bq9a8al4.fsf@jidanni.org> (jidanni@jidanni.org's message of "Sun, 02 Dec 2007 03:43:35 +0800")
On Sat, Dec 01 2007, jidanni@jidanni.org wrote:
> Does gnus make a "From" line with less information than it could?
> $ diff /home/jidanni/.procmail/backup/msg.3DT file_saved_with_gnus-summary-save-article
> 1c1
> < From dans.mom@comcast.net Sun Dec 02 03:07:43 2007
> ---
> > From nobody Sun Dec 2 03:24:38 2007
> Or is it no big deal as it is merely a separator, created with
> information already in the headers below it?
It's a just separator, AFAIK.
Maybe it could use the mail and date for the From_ line. I think the
relevant function is `gnus-output-to-mail' in `gnus-util.el'.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
parent reply other threads:[~2007-12-01 23:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87bq9a8al4.fsf@jidanni.org>]
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=v9d4tq3sao.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=bugs@gnus.org \
--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).