From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Gnus: How to reference an article from a gmane mailing list
Date: Sun, 05 Dec 2021 19:56:26 +0100 [thread overview]
Message-ID: <87lf0yq3s5.fsf@gmail.com> (raw)
In-Reply-To: <86sfv76rqq.fsf@duenenhof-wilhelm.de> (H. Dieter Wilhelm's message of "Sun, 05 Dec 2021 15:39:09 +0100")
Hi Dieter,
Assuming the "references" you're interested in are message IDs,
"H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de> writes:
> But when I would like to refer to a post in another threat?
While reading a post (or "article" in Gnusspeak) in the summary buffer,
you can hit "C-u g" to see the raw message; somewhere in there you'll
see this header:
> Message-ID: <86sfv76rqq.fsf@duenenhof-wilhelm.de>
Not sure if Gnus has a keybinding to copy them without going through
"C-u g"; FWIW I've written this small helper:
(defun my/kill-message-id ()
(interactive)
(kill-new (mail-header-message-id (gnus-summary-article-header))))
I haven't tried it, but you could probably also add "^Message-Id:" to
gnus-visible-headers.
Last option that I know of: if you're looking at the mailing list's web
archives, e.g. here:
https://lists.gnu.org/archive/html/help-gnu-emacs/2021-12/msg00103.html
You'll see a comment in the HTML source with this same message ID:
> <!--X-Message-Id: 86sfv76rqq.fsf@duenenhof-wilhelm.de -->
> And I would
> like you to be able to read (or at least find) this article as well.
> How to do that?
Two ways that I know of:
- Gnus adds buttons on top of message IDs, so either clicking those or
TAB'ing your way to them and hitting RET will fetch the corresponding
article,
- "j" in the summary buffer will prompt for a message ID and fetch it.
Hope that helps.
next prev parent reply other threads:[~2021-12-05 18:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 13:26 Gnus: How to reference an article from a gmane mailing list H. Dieter Wilhelm
2021-12-05 14:21 ` Byung-Hee HWANG
2021-12-05 14:39 ` H. Dieter Wilhelm
2021-12-05 15:09 ` Byung-Hee HWANG
2021-12-08 11:19 ` Byung-Hee HWANG
2021-12-05 18:56 ` Kévin Le Gouguec [this message]
2021-12-05 21:24 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-05 21:51 ` Kévin Le Gouguec
2021-12-06 2:30 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-07 23:17 ` H. Dieter Wilhelm
2021-12-07 23:57 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-08 6:01 ` H. Dieter Wilhelm
2021-12-08 0:10 ` Michael Heerdegen
2021-12-08 0:37 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-08 6:14 ` H. Dieter Wilhelm
2021-12-08 6:39 ` Michael Heerdegen
2021-12-08 6:43 ` Michael Heerdegen
2021-12-08 6:50 ` Michael Heerdegen
2021-12-08 7:22 ` Kévin Le Gouguec
2021-12-08 8:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-10 18:30 ` H. Dieter Wilhelm
2021-12-11 1:27 ` Michael Heerdegen
2021-12-11 8:03 ` Yuri Khan
2021-12-12 22:14 ` H. Dieter Wilhelm
2021-12-12 23:17 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-13 17:38 ` H. Dieter Wilhelm
2021-12-13 19:46 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-05 18:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=87lf0yq3s5.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=dieter@duenenhof-wilhelm.de \
--cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).