From: Eric Abrahamsen <firstname.lastname@example.org>
To: Kyle Meyer <email@example.com>
Subject: Re: yhetil.org/orgmode now supports searching by Gmane ID
Date: Wed, 22 Apr 2020 22:34:16 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Kyle Meyer's message of "Thu, 23 Apr 2020 04:58:34 +0000")
Kyle Meyer <firstname.lastname@example.org> writes:
> Eric Abrahamsen <email@example.com> writes:
>> Kyle Meyer <firstname.lastname@example.org> writes:
>>> $ w3m -m nntp://news.gmane.io/gmane.emacs.orgmode/112052
>>> (Offhand I don't know how to do the same in Gnus, despite it being my
>>> primary method for following things over nntp.)
>> I assume you can just use "j" in the summary buffer, and enter the
>> article number. Doing that for message 112052 got me message-id
>> "<email@example.com>", is that correct?
> That's the one. Thanks!
> If you happen to know off the top of your head: Is there an easy way for
> me to jump to that article if I'm not subscribed to the
> gmane.emacs.orgmode group but have the nntp:news.gmane.io server set up
> (for other lists)?
Hmm, this isn't something I do very often, but I think if you make an
ephemeral group with either "B" or "G M" (the interfaces are different,
but I believe the result is the same) you can enter the group name,
specify that it should use your nntp:news.gmane.io server, then the
group will open and you can do the "j" trick. The group should disappear
from your Gnus installation when you're done with it. You could also
write your own wrapper around gnus-group-read-ephemeral-group.
It might take some experimentation!
next prev parent reply other threads:[~2020-04-23 5:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 4:43 yhetil.org/orgmode now supports searching by Gmane ID Kyle Meyer
2020-04-23 4:46 ` Eric Abrahamsen
2020-04-23 4:58 ` Kyle Meyer
2020-04-23 5:34 ` Eric Abrahamsen [this message]
2020-05-21 7:24 ` Bastien
2020-05-23 0:01 ` Kyle Meyer
2020-05-24 12:05 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).