From: Yuri Khan <yuri.v.khan@gmail.com>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>,
help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Gnus: How to reference an article from a gmane mailing list
Date: Sat, 11 Dec 2021 15:03:17 +0700 [thread overview]
Message-ID: <CAP_d_8Wqdqg2Hg76QNPry9eTrQ0KZWO+aMhuo5OY94io-j9uig@mail.gmail.com> (raw)
In-Reply-To: <874k7j7e8u.fsf@gmail.com>
On Wed, 8 Dec 2021 at 14:23, Kévin Le Gouguec <kevin.legouguec@gmail.com> wrote:
> > Oh wait! What about Gmail or other mail readers of Emacs, do they have
> > this functionality as well?
>
> Can't tell you 😕 I'd be very (though pleasantly) surprised if GMail
> could work with Message IDs; as for other mail readers, I just don't
> know.
Gmail can search by Message-ID, although the syntax is somewhat hard
to remember and it’s not exposed in the UI, you have to dig into help
to find it. The keyword is:
rfc822msgid:874k7j7e8u.fsf@gmail.com
On the other hand, forward lookup is straightforward: on a message,
clicking the ‘More’ menu and selecting ‘Show original’ opens the
message source form in a new tab, with the Message-ID right there on
the top, you don’t even have to scan the headers to look for it.
Thunderbird lets you search by any headers. You press Ctrl+Shift+F to
open the search dialog, then, in the ‘Match all of the following’
section, you have to pull down the field selector and, if Message-ID
is not there (by default), select Customize…, enter Message-ID and
click Add. This is a one-time setup, after that, it should be listed
in the pulldown.
To look up a message’s Message-ID header, you open its source (Ctrl+U)
and look for the header.
next prev parent reply other threads:[~2021-12-11 8:03 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
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 [this message]
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=CAP_d_8Wqdqg2Hg76QNPry9eTrQ0KZWO+aMhuo5OY94io-j9uig@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=dieter@duenenhof-wilhelm.de \
--cc=help-gnu-emacs@gnu.org \
--cc=kevin.legouguec@gmail.com \
/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).