From: Leo Butler <l.butler@cmich.edu>
To: info-gnus-english@gnu.org
Subject: Re: gnus-summary-line-format for outboxes
Date: Wed, 05 Sep 2012 17:12:08 -0400 [thread overview]
Message-ID: <86sjaw8993.fsf@mth-pe120-ux01.butler.org> (raw)
In-Reply-To: <87pq60s4kv.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Leo Butler <l.butler@cmich.edu> writes:
>
>> I am curious as to how one sets gnus-summary-line-format `corrrectly' for an
>> email outbox? Is is really necessary create a user-defined function to
>> fish the To field out of the header information?
>
> No, I think Gnus will show the To header instead of the From header by
> default now. If the backend gives Gnus the required information, which
> most of them do.
Even with the tip of the master branch, Gnus was not showing the To
header. Adam's advice did work for me, though. Thanks, Leo.
next prev parent reply other threads:[~2012-09-05 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.8149.1346868912.855.info-gnus-english@gnu.org>
2012-09-05 18:32 ` Lars Ingebrigtsen
2012-09-05 21:12 ` Leo Butler [this message]
2012-09-04 22:04 Leo Butler
2012-09-05 18:33 ` Adam Sjøgren
2012-09-05 21:06 ` Leo Butler
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=86sjaw8993.fsf@mth-pe120-ux01.butler.org \
--to=l.butler@cmich.edu \
--cc=info-gnus-english@gnu.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).