From: Roland Winkler <winkler@gnu.org>
To: info-gnus-english@gnu.org
Subject: Re: Retrieve thread URL from Gnus
Date: Wed, 23 Mar 2022 10:14:12 -0500 [thread overview]
Message-ID: <87mthg1z23.fsf@gnu.org> (raw)
In-Reply-To: <87zglgbue0.fsf@tullinup.koldfront.dk>
On Wed, Mar 23 2022, Adam Sjøgren wrote:
> The equivalent is:
>
> a) Open the news.gmane.io server: in the Group buffer press B RET (for
> nntp) and enter news.gmane.io
> b) Find the group gmane.lisp.clisp.devel and enter it (press RET with
> point on the line)
> c) Jump to article number: press j and enter the article number
>
> If you want to see the entire thread, you can press A T to have the
> other articles in the thread inserted into the *Summary* buffer.
>
> If you find it convenient to read news (i.e. mailing lists) via gmane,
> you can set it up as a permanent server in your Gnus configuration
> (gnus-secondary-methods) and subscribe to the groups you like to read.
Thanks, yes, I just realized that yesterday I fooled myself. I am
already reading news via gnus, but yesterday I messed up from which
group I was looking for an old article. Then I got confused that gnus
article numbers did not match what I was expecting to get and what I did
get as expected in the telnet session. Entirely my fault!
But you are right: sometimes it is fun to go back to the basics and live
like a caveman!
next prev parent reply other threads:[~2022-03-23 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 14:38 André A. Gomes
2022-03-22 17:13 ` Adam Sjøgren
2022-03-22 19:09 ` André A. Gomes
2022-03-22 19:15 ` Adam Sjøgren
2022-03-23 13:58 ` Roland Winkler
2022-03-23 14:44 ` Adam Sjøgren
2022-03-23 15:14 ` Roland Winkler [this message]
2022-03-24 14:42 ` Byung-Hee HWANG
2022-04-29 8:38 ` TRS-80
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mthg1z23.fsf@gnu.org \
--to=winkler@gnu.org \
--cc=info-gnus-english@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 NNTP newsgroup(s).