From: Roland Winkler <winkler@gnu.org>
To: Sam Steingold <sds@gnu.org>
Cc: bbdb-user@nongnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
54423@debbugs.gnu.org
Subject: bug#54423: 29.0.50; gnus-fetch-original-field returns nil in digest
Date: Thu, 17 Mar 2022 14:40:56 -0500 [thread overview]
Message-ID: <874k3w2wqf.fsf__33334.9120848411$1647546140$gmane$org@gnu.org> (raw)
In-Reply-To: <lzilsctx5r.fsf@3c22fb11fdab.ant.amazon.com> (Sam Steingold's message of "Thu, 17 Mar 2022 11:29:36 -0400")
On Thu, Mar 17 2022, Sam Steingold wrote:
> the problem is that `bbdb-message-header' calls
> `gnus-fetch-original-field' which, for a digest group, returns nil.
> This prevents `bbdb-accept-message-alist' from working for, e.g.,
>
> (("Newsgroups" . "\\(gmane\\.emacs\\|gmane\\.comp\\.security\\.risks\\)"))
>
> because every message in gmane.comp.security.risks is a digest.
While I included the call of `gnus-fetch-original-field' in
`bbdb-message-header', I need to admit that the above issue goes much
beyond my knowledge of Gnus internals. If there are better ways for
`bbdb-message-header' to achieve what it needs to achieve (which is
grabbing the content of (what appear to be) headers of a message),
then I certainly appreciate any patches for BBDB.
Roland
next prev parent reply other threads:[~2022-03-17 19:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 15:13 bug#54423: 29.0.50; gnus-fetch-original-field returns nil in digest Sam Steingold
2022-03-17 10:59 ` Lars Ingebrigtsen
2022-03-17 12:06 ` Lars Ingebrigtsen
2022-03-17 15:24 ` Sam Steingold
2022-03-17 15:35 ` Lars Ingebrigtsen
2022-03-22 0:04 ` Sam Steingold
[not found] ` <lzfsnaj1i2.fsf@3c22fb11fdab.ant.amazon.com>
2022-03-22 16:49 ` Roland Winkler
2022-03-17 15:29 ` Sam Steingold
[not found] ` <lzilsctx5r.fsf@3c22fb11fdab.ant.amazon.com>
2022-03-17 19:40 ` Roland Winkler [this message]
[not found] ` <874k3w2wqf.fsf@gnu.org>
2022-03-17 19:43 ` Lars Ingebrigtsen
2022-03-17 19:51 ` Roland Winkler
2022-03-17 20:09 ` Sam Steingold
2022-03-17 20:24 ` Lars Ingebrigtsen
2022-03-21 20:25 ` Sam Steingold
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='874k3w2wqf.fsf__33334.9120848411$1647546140$gmane$org@gnu.org' \
--to=winkler@gnu.org \
--cc=54423@debbugs.gnu.org \
--cc=bbdb-user@nongnu.org \
--cc=larsi@gnus.org \
--cc=sds@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).