unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Roland Winkler <winkler@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: bbdb-user@nongnu.org, Sam Steingold <sds@gnu.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:51:19 -0500	[thread overview]
Message-ID: <87lex81hoo.fsf__33382.4438437418$1647546736$gmane$org@gnu.org> (raw)
In-Reply-To: <87sfrgqs9t.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 17 Mar 2022 20:43:26 +0100")

On Thu, Mar 17 2022, Lars Ingebrigtsen wrote:
> If the intention is to collect data from the parent group (which is a
> thing mostly just for nndoc groups), you first have to determine what
> the parent group is, and then you can select the data from the buffer
> that's named something like " *Original Article group.name*".

Thanks for the clarification! - This brings me back to what I said: if
someone more knowledgable of Gnus internals can translate the above into
code for `bbdb-message-header', I'll appreciate that.  I can also try do
that myself.  But then I cannot promise anything.





  reply	other threads:[~2022-03-17 19:51 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
     [not found]     ` <874k3w2wqf.fsf@gnu.org>
2022-03-17 19:43       ` Lars Ingebrigtsen
2022-03-17 19:51         ` Roland Winkler [this message]
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='87lex81hoo.fsf__33382.4438437418$1647546736$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).