From: Max Nikulin <manikulin@gmail.com>
To: 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: Mon, 24 Jul 2023 21:54:01 +0700 [thread overview]
Message-ID: <u9m3a9$1634$1@ciao.gmane.io> (raw)
In-Reply-To: <b0d3fee0-0dc9-a7ee-32dd-478297cb6b2d@vodafonemail.de>
On 23/07/2023 21:13, Jens Schmidt wrote:
> Gnus can have a global Message-ID cache, but it's not on by default (at
> least not in Emacs 28, haven't checked others). And anyway, it's a
> potentially incomplete *cache*, and not an *index*.
Thank you for clarification. Certainly just Message-ID is not enough
without the index.
> For nntp groups you already have the option to store links as web links
> to groups.google.com, by means of `org-gnus-prefer-web-links'.
I believe that links may be converted to web archives either to open or
to export them. In a document I would prefer a more general form like
news://news.gmane.io/gmane.emacs.orgmode/b0d3fee0-0dc9-a7ee-32dd-478297cb6b2d@vodafonemail.de
though group name is redundant.
In Thunderbird links to known articles work reasonably well
<mid:b0d3fee0-0dc9-a7ee-32dd-478297cb6b2d@vodafonemail.de>
I do not think, mid: links are ideal, but it is off-topic in this thread.
For storing links I would avoid volatile parts like mail folder where a
message *currently* resides or name of virtual folder/group specific to
user configuration as well as application-specific URIs.
I admit that due to gnus design, group names are unavoidable for some
backends. I do not see a better way than the approach implemented in the
suggested patch.
next prev parent reply other threads:[~2023-07-24 14:55 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
2023-07-23 14:13 ` Jens Schmidt
2023-07-24 14:54 ` Max Nikulin [this message]
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='u9m3a9$1634$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@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.
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).