From: Max Nikulin <manikulin@gmail.com>
To: Jens Schmidt <jschmidt4gnu@vodafonemail.de>, emacs-orgmode@gnu.org
Subject: Re: [BUG] Issues in ol-gnus when storing links in nnvirtual and nnselect articles [9.7-pre (release_9.6.7-570-gd6f3ae.dirty @ /home/jschmidt/work/org-mode/lisp/)]
Date: Sun, 23 Jul 2023 17:26:24 +0700 [thread overview]
Message-ID: <d6e7dbc6-2757-28aa-faeb-e08d2bf3d717@gmail.com> (raw)
In-Reply-To: <2fa5914d-2cbf-f41f-8be6-e79e77794140@vodafonemail.de>
On 22/07/2023 16:06, Jens Schmidt wrote:
> - Create an nnselect group and open an article from that. In the
> article buffer, do M-x org-store-link RET, then paste the link with
> C-c C-l in some Org mode buffer. The resulting link looks like
>
> gnus:#E18xcfu-0004HT-00@fencepost.gnu.org
>
> That is, it lacks the group name before the hash sign. Correct would
> have been:
>
> gnus:nnml+archive:test01#E18xcfu-0004HT-00@fencepost.gnu.org
I am not a gnus user, so my comments may be irrelevant due to my
ignorance. In that case I am sorry.
Is nnselect a real NNTP group or is it some instance existing solely in
user's configuration? Does gnus have global Message-ID index?
Generally news group is not necessary to specify a message on a NNTP
server, it may be retrieved by Message-ID only. The name of the news
group is mandatory if *article number* is used.
(info "(url) news/nntp/snews") or <info:url#news/nntp/snews> or
https://www.gnu.org/software/emacs/manual/html_node/url/news_002fnntp_002fsnews.html
I am curious whether namely "gnus" links have to be used or it is
possible to rely on more generic "news:"/"nntp:" links, or even
<mid:E18xcfu-0004HT-00@fencepost.gnu.org> (perhaps with some
`browse-url' configuration)? It should improve portability.
next prev parent reply other threads:[~2023-07-23 10:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 9:06 [BUG] Issues in ol-gnus when storing links in nnvirtual and nnselect articles [9.7-pre (release_9.6.7-570-gd6f3ae.dirty @ /home/jschmidt/work/org-mode/lisp/)] Jens Schmidt
2023-07-22 13:48 ` Ihor Radchenko
2023-07-22 15:37 ` Jens Schmidt
2023-07-22 21:09 ` Eric Abrahamsen
2023-07-23 6:45 ` Ihor Radchenko
2023-07-24 1:55 ` Eric Abrahamsen
2023-07-24 7:17 ` Ihor Radchenko
2023-07-24 20:23 ` Jens Schmidt
2023-07-25 7:16 ` Ihor Radchenko
2023-07-27 16:10 ` Eric Abrahamsen
2023-07-23 10:26 ` Max Nikulin [this message]
2023-07-23 14:13 ` Jens Schmidt
2023-07-24 14:54 ` Max Nikulin
2023-07-26 16:04 ` Ihor Radchenko
2023-07-26 19:36 ` Jens Schmidt
2023-07-27 7:56 ` Ihor Radchenko
2023-07-28 11:27 ` Bastien Guerry
2023-07-29 7:04 ` Ihor Radchenko
2023-07-30 15:57 ` Jens Schmidt
2023-07-30 16:35 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d6e7dbc6-2757-28aa-faeb-e08d2bf3d717@gmail.com \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jschmidt4gnu@vodafonemail.de \
/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/org-mode.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).