emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: gnus: link annoyance
Date: Mon, 06 Jan 2014 11:39:46 -0500	[thread overview]
Message-ID: <87k3edcbe5.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: 87zjn9w79w.fsf@iro.umontreal.ca

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

Maybe I'm misunderstanding (not deliberately, I assure you) what you
mean but 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. It's only
expired articles that can never be gotten back after their expiration
period runs out.

But maybe that's what you are alluding to when you say "visiting the
group in a regular way"?

Nick

  reply	other threads:[~2014-01-06 16:40 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 [this message]
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=87k3edcbe5.fsf@alphaville.bos.redhat.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).