From: Bob Newell <bobnewell@bobnewell.net>
To: info-gnus-english@gnu.org
Subject: Re: question about org-link gnus message and gnus registry
Date: Wed, 01 Dec 2021 13:47:50 -1000 [thread overview]
Message-ID: <871r2vvqe1.fsf@emailmessageidheader.nil> (raw)
In-Reply-To: <87o860krsm.fsf@googlemail.com> (physiculus@gmail.com's message of "Wed, 01 Dec 2021 21:12:57 +0100")
physiculus <physiculus@gmail.com> writes:
>
> scenario:
> i create a org link with org and insert the link into an org file.
> works.
>
> now i move the message inside gnus to another folder.
>
> open the link inside the org file is not valid anymore.
Without getting into unknown territory about why this is, I
have encountered the same problem.
I have a solution that applies only to gmail, so it may not
help. I have some elisp that runs as a hook after a gnus
org-mode link is created, and changes (for instance) "Inbox"
to "All Mail". This takes advantage of the fact that
everything in gmail is always in "All Mail" so the org link is
always valid.
Something similar for non-gmail probably could be cooked up if
you're willing to move the item in question to a common folder
such as an archive.
I don't say that this is a substitute for actually figuring
things out. I have tried Gnorb which tracks via the registry
but never completely got it to be as general as I wished.
--
Bob Newell
Honolulu, Hawai`i
- Via GNU/Linux/Emacs/Gnus/BBDB
next prev parent reply other threads:[~2021-12-01 23:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 20:12 physiculus
2021-12-01 23:47 ` Bob Newell [this message]
2021-12-02 19:07 ` physiculus
2021-12-02 19:20 ` Eric Abrahamsen
2021-12-02 19:35 ` physiculus
2021-12-02 21:29 ` Eric Abrahamsen
2021-12-02 21:42 ` Michael Heerdegen
2021-12-02 21:44 ` Michael Heerdegen
2021-12-02 22:42 ` Eric Abrahamsen
2021-12-02 22:46 ` Michael Heerdegen
2021-12-03 0:30 ` Eric Abrahamsen
2021-12-03 1:50 ` Michael Heerdegen
2021-12-03 1:57 ` Eric Abrahamsen
2021-12-03 3:18 ` Eric Abrahamsen
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=871r2vvqe1.fsf@emailmessageidheader.nil \
--to=bobnewell@bobnewell.net \
--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).