From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: gnus: link annoyance
Date: Mon, 06 Jan 2014 08:48:27 -0500 [thread overview]
Message-ID: <87zjn9w79w.fsf@iro.umontreal.ca> (raw)
Hi, Org people.
Still playing with one of my little tools (called org-grep), I added the
capability of searching Unix mailbox (producing "rmail:" links) and Gnus
mailgroups (producing "gnus:" links). This resurrected an old "gnus:"
annoyance I once reported on this mailing list, yet without being able
to convince anybody there was a problem. I dare trying again! :-)
Whenever I visit a "gnus:" type link from Org, it has the side effect of
"reading" the article in Gnus parlance, forcing me to "unread" it each
time afterwards. If I forget to unread it, which is a likely error, the
article will not be shown if I later visit its mailgroup using Gnus in a
regular way. So in practice, it is kind of forever lost.
This is a sad side-effect of "gnus:" links. In this area, Org should
immediately unread any "gnus:" link it follows, or else and maybe even
better, leave the reached article with the flags it already has. If the
user explicitly saved the article in an Org file using "org-store-link",
(s)he surely though of it as kind of permanent, and Org should then not
"read" it, even the user did not "bang" it. If the link is dynamically
created like with org-grep, and the user happens to follow one of these
links among many others, the user should not be "punished" by loosing
the article because (s)he forgot to explicitly unread it :-).
François
P.S. Who also has a question about "rmail:" and "gnus:" links. Is there
a way in the link syntax allowing a precise line positioning within the
article? It would be wonderful for org-grep, that would then make great
use of such a possibility.
next reply other threads:[~2014-01-06 13:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 13:48 François Pinard [this message]
2014-01-06 16:39 ` gnus: link annoyance Nick Dokos
2014-01-07 5:14 ` François Pinard
2014-01-07 12:07 ` Nick Dokos
2014-01-07 15:28 ` François Pinard
2014-01-07 19:06 ` Achim Gratz
2014-01-08 1:37 ` François Pinard
2014-01-08 15:15 ` Bastien
2014-01-06 17:05 ` Rasmus
2014-01-07 5:36 ` François Pinard
2014-01-07 9:00 ` Bastien
2014-01-07 14:13 ` François Pinard
2014-01-07 13:01 ` Rasmus
2014-01-07 14:34 ` François Pinard
2014-01-07 13:28 ` Joseph Vidal-Rosset
2014-01-07 15:02 ` François Pinard
2014-01-07 17:09 ` Joseph Vidal-Rosset
2014-01-07 17:43 ` Nick Dokos
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=87zjn9w79w.fsf@iro.umontreal.ca \
--to=pinard@iro.umontreal.ca \
--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).