From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: ding@gnus.org
Subject: Re: githubs notifications (different authors) and the froms in the summary buffer are a bit confusing
Date: Thu, 02 Dec 2021 16:05:23 +0000 [thread overview]
Message-ID: <87pmqfat6k.fsf@gnus.jao.io> (raw)
In-Reply-To: <87zgpjsbco.fsf@mat.ucm.es>
On Thu, Dec 02 2021, Uwe Brauer wrote:
[...]
> So it seems that %U is the culprit here. That however seems difficult to
> Any idea how to do that?
A way is to define your own format function. For instance, i have this
function to display the from address with anything matching the regexp
jao-gnus--news-rx removed:
(defun gnus-user-format-function-f (headers)
(let* ((from (gnus-header-from headers))
(from (gnus-summary-extract-address-component from)))
(replace-regexp-in-string jao-gnus--news-rx "" from)))
the `-f' at the end or the name matters, it's the code to use in the
line format: "... %uf ..." stands for "user-defined function f"
hope this helps,
jao
--
"We must do something. This is something. Therefore, we must do this."
- Antony Jay and Jonathan Lynn, "Yes Minister"
next prev parent reply other threads:[~2021-12-02 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 7:40 Uwe Brauer
2021-12-02 16:05 ` Jose A. Ortega Ruiz [this message]
2021-12-03 9:58 ` Uwe Brauer
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=87pmqfat6k.fsf@gnus.jao.io \
--to=jao@gnu.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).