From: Nigel Beck <me@nigelbeck.com>
To: info-gnus-english@gnu.org
Subject: getting who its TO rather than FROM in the sent folder summary
Date: Wed, 24 Feb 2010 10:26:59 -0500 [thread overview]
Message-ID: <873a0qpscc.fsf@bsdlaptop.bsdlaptop.danakil.selfip.com> (raw)
My understanding is that if gnus-ignored-from-addresses is set to, eg,
"Nigel Beck", or some regex of underlying email addresses, that the
summary buffer for my sent items group(s) would show who the mail is
TO... but, alas, no such luck.
1) Is it my summary line format?
My summary line format is
(setq gnus-summary-line-format
(concat "%U%R %~(pad-right 2)t%* %uj %B%~(max-right 20)~(pad-right 20)n "
"%~(max-right 40)~(pad-right 40)s %-80=%&user-date;\n"))
where user function j just marks whether its TO me or CC me, and user
date pretties up the dates a little. Is "~n" not the right thing here?
2) Is something cached here, where I need to refresh the sent items
group somehow?
3) Option three....?
--
Nigel Beck
http://www.nigelbeck.com
next reply other threads:[~2010-02-24 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 15:26 Nigel Beck [this message]
2010-02-25 8:07 ` Reiner Steib
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=873a0qpscc.fsf@bsdlaptop.bsdlaptop.danakil.selfip.com \
--to=me@nigelbeck.com \
--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).