From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: gnus: link annoyance
Date: Tue, 07 Jan 2014 07:07:01 -0500 [thread overview]
Message-ID: <87wqic0zdm.fsf@gmail.com> (raw)
In-Reply-To: 87lhys2x24.fsf@iro.umontreal.ca
François Pinard <pinard@iro.umontreal.ca> writes:
> Nick Dokos <ndokos@gmail.com> writes:
>
>> François Pinard <pinard@iro.umontreal.ca> writes:
>
>>> 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.
>
>> it's certainly not lost: the link continues to work, even if it points
>> to a read article; and visiting the group with C-u <SPACE> in gnus
>> also allows you to see previously read articles.
>
> Hi, Nick.
>
> Of course, you are fully right in that the article is still there, and
> likely unexpired. But in practice, from my viewpoint, it is not there
> anymore: I do not usually enter groups by C-u SPC. While possible, it
> is unusual that I want to find and read again an article which I once
> decided has been read for good.
>
The question is how one deals with those unusual cases where you do want
to revisit an article (or a mail message: to gnus they are the same thing).
> If I search all mailgroups for a certain string, and randomly check
> hits, I do not want these articles I check to later have disappeared
> from sight in practice. I was not really in the process of reading
> articles, but merely checking on them.
You call it checking but you are really reading them: how exactly is org
or gnus to know that even though you are reading the articles, you are
not really reading them?
> It would not make sense that Org removes lines that I visit after a
> grep, and when grepping through many files, would they be Org,
> non-Org, mailboxes or articles in mailgroups, I am in a mode where I
> do not expect any kind of altering behaviour.
>
But it doesn't: the links in the org file still work. In any case,
you must have read the article in order to determine that you want to
save a link to it. Then following the link does not change the flags:
it was read before, it's still read after.
I suspect however that my arguments are going to convince you just as
much as your arguments have convinced me :-)
--
Nick
next prev parent reply other threads:[~2014-01-07 12:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 13:48 gnus: link annoyance François Pinard
2014-01-06 16:39 ` Nick Dokos
2014-01-07 5:14 ` François Pinard
2014-01-07 12:07 ` Nick Dokos [this message]
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=87wqic0zdm.fsf@gmail.com \
--to=ndokos@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).