From: Lars Ingebrigtsen <larsi@gnus.org>
To: Sam Steingold <sds@gnu.org>
Cc: 54423@debbugs.gnu.org
Subject: bug#54423: 29.0.50; gnus-fetch-original-field returns nil in digest
Date: Thu, 17 Mar 2022 11:59:43 +0100 [thread overview]
Message-ID: <87ee30vo80.fsf@gnus.org> (raw)
In-Reply-To: <lzr172szfa.fsf@3c22fb11fdab.ant.amazon.com> (Sam Steingold's message of "Wed, 16 Mar 2022 11:13:45 -0400")
Sam Steingold <sds@gnu.org> writes:
> In the group gmane.comp.security.risks on server nntp:news.gmane.io open
> an article and type C-d (gnus-summary-enter-digest-group).
> Then enter a message from the summary buffer (e.g., SPC)
> and now (gnus-fetch-original-field "Newsgroups") returns nil instead of
> "gmane.comp.security.risks" as it should.
> The variable gnus-original-article-buffer evaluates to
> " *Original Article gmane.comp.security.risks*"
> and that buffer starts like this:
I think there's a misunderstanding here -- the "original" that the
function is fetching is the unformatted "original" version of the thing
that's displayed in the *Article* buffer. It has nothing to do with how
the article was sourced (which was via a digest in this case).
So this is working as designed.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-03-17 10:59 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 [this message]
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
[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=87ee30vo80.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=54423@debbugs.gnu.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).