emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Linking by Message-ID
Date: Wed, 6 Apr 2022 00:08:16 +0700	[thread overview]
Message-ID: <t2ht21$12r5$1@ciao.gmane.io> (raw)
In-Reply-To: <87ee2cf45u.fsf@localhost>

On 05/04/2022 13:14, Ihor Radchenko wrote:
> Karl Fogel writes:
>>>>    From: Ihor Radchenko
>>>>    Subject: Re: Removing obsolete function
>>>>    `org-truely-invisible-p'.
>>>>    To: Karl Fogel
>>>>    Cc: Org Mode
>>>>    Date: Sun, 19 Dec 2021 17:14:32 +0800
>>>>    Message-ID: <87h7b5rm6f.fsf@localhost>
>>> I usually just leave an ML link in such cases:
>>> https://orgmode.org/list/87h7b5rm6f.fsf@localhost
>> As long as the ML link contains the Message-ID, as appears to be
>> the case here, yeah.  Mailing list archives can move, which causes
>> links to suddenly stop working.  But if the Message-ID is in the
>> link, then (with a little extra work) one can always find the
>> message in the new archive.
>> (The reason I typically include more is to make things as easy as
>> possible for those who are searching in a local archive using
>> their regular mailreader.  But I can switch to the above way if
>> you'd prefer.)
> FYI, I do not know an easy way to search mailing list archives by
> Message-ID. Message-ID itself does not even provide information which
> mailing list it is referring to (maybe it is e.g. Emacs devel).
> That's why I prefer links - they can often be found using archive.org if
> nothing.
> On the other hand, extra information would not heart. In addition to
> link.

A link to a message in the local storage of a regular mail reader should 
have mid: scheme, e.g. mid:87h7b5rm6f.fsf@localhost
RFC 2392 - Content-ID and Message-ID Uniform Resource Locators

Unfortunately the only way to specify mail list is the text around the link.

Mail-archive promises Message-ID resolver 
https://mid.mail-archive.com/... but it does not work for emacs-orgmode. 
Gmane has the org mail list archive and allows access using Message-ID 
from an arbitrary mail list:

     w3m -m 'nntp://news.gmane.io/87h7b5rm6f.fsf@localhost'

However I consider https://list.orgmode.org/MID links as more friendly 
for users unaware of possible ways to obtain some message using its 

  reply	other threads:[~2022-04-05 17:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-04 20:53 Removing obsolete function `org-truely-invisible-p' Karl Fogel
2021-12-04 22:19 ` Samuel Wales
2021-12-19  9:14 ` Ihor Radchenko
2022-04-01  0:28   ` Karl Fogel
2022-04-04 11:55     ` Ihor Radchenko
2022-04-04 16:20       ` Karl Fogel
2022-04-05  6:14         ` Ihor Radchenko
2022-04-05 17:08           ` Max Nikulin [this message]
2022-04-05 18:41           ` Karl Fogel
2022-04-07  4:59             ` Ihor Radchenko
2022-04-07 16:57               ` Karl Fogel
2022-04-15  9:33                 ` [PATCH] CONTRIBUTE: Link WORG page when explaining commit message format Ihor Radchenko
2022-04-15 12:47                   ` Robert Pluim
2022-04-15 21:13                     ` Karl Fogel
2022-04-16  9:35                     ` Ihor Radchenko
2022-04-23  8:06                   ` Ihor Radchenko
2022-04-23 15:47                     ` Karl Fogel

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:

  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='t2ht21$12r5$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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).