From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Re: gnus: link annoyance
Date: Tue, 07 Jan 2014 10:28:00 -0500 [thread overview]
Message-ID: <87wqibdd6n.fsf@iro.umontreal.ca> (raw)
In-Reply-To: <87wqic0zdm.fsf@gmail.com> (Nick Dokos's message of "Tue, 07 Jan 2014 07:07:01 -0500")
Nick Dokos <ndokos@gmail.com> writes:
> I suspect however that my arguments are going to convince you just as
> much as your arguments have convinced me :-)
Hi, Nick. You know, it always has been a pleasure corresponding with
you, and enjoying your respectful attitude. In the case here, I'm not
so trying to convince you, than to alleviate a bit of my misery! :-)
> 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).
Well, using Gnus interactively or through Emacs Lisp programming does
not have to be the same thing, programs may bend Gnus behaviour.
> 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?
Org could tell Gnus that I am not really reading an article as if I was
using Gnus interactively. When a user interactively created an Org link
to a Gnus article (likely using C-c l), (s)he decided at the time if the
article was to be left read, unread, ticked or otherwise. The human
decision has been taken at the time the Org link was created. When Org
later visits that link and triggers Gnus into displaying the article, it
could get Gnus to do nothing else then display it, keeping the prior
human decision unaltered, defeating a Gnus automatism that mainly make
sense when reading interactively from Gnus (and not from Org), leaving
the responsibility to the user to explicitly change the prior human
decision if this is then deemed appropriate.
> the links in the org file [to previously read articles] still work.
Which is wonderful, indeed. I can read an article, leave it "read", and
still save a working Org link on a article who disappeared out of sight.
> 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.
Exactly! :-) Your last sentence summarizes all of my desires! But I
would complete it, just to make sure it extremely clear:
Then following the link does not change the flags: it was read
before, it's still read after; it was unread before, it's still
unread after.
Hoping that you forgive my friendly tease! Keep happy!
François
next prev parent reply other threads:[~2014-01-07 15:28 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
2014-01-07 15:28 ` François Pinard [this message]
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=87wqibdd6n.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).