emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: gnus: link annoyance
Date: Mon, 06 Jan 2014 18:05:32 +0100	[thread overview]
Message-ID: <874n5hca77.fsf@pank.eu> (raw)
In-Reply-To: 87zjn9w79w.fsf@iro.umontreal.ca

Hi François,

Thanks for working on org-grep.  It looks interesting.

Excuse me if I misunderstood something below.

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

You read it, no?  How can it not be marked read when you read it?

Perhaps you would like to the following on mailgroups you care about
(from the *Groups* buffer):

    G c C-s Display S-TAB RET TAB RET 1 TAB 100 M-< TAB TAB RET

Also, you can search with nnir using GG or C-u GG (but links probably
won't work from a nnir buffer).
    
> 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.

I cannot reproduce using the following receipt: 

  1. Mark an article as important with '!',
     (gnus-summary-tick-article-forward N)
  1. (org-store-link)
  2. org-insert-link with the above link in org-buffer
  3. Open link.  My tick is preserved.

I can also change the mark to gnus-summary-mark-as-expirable and
preserve the link.  I cannot preserve an unread mark when I read it,
but it shouldn't 'cause I read the article. . .

Cheers,
Rasmus

--
When the facts change, I change my mind. What do you do, sir?

next prev parent reply	other threads:[~2014-01-06 17:02 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
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 [this message]
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=874n5hca77.fsf@pank.eu \
    --to=rasmus@gmx.us \
    --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

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