From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Re: gnus: link annoyance
Date: Tue, 07 Jan 2014 20:37:08 -0500 [thread overview]
Message-ID: <87mwj7w8xn.fsf@iro.umontreal.ca> (raw)
In-Reply-To: <87y52r4noi.fsf@Rainer.invalid> (Achim Gratz's message of "Tue, 07 Jan 2014 20:06:05 +0100")
Achim Gratz <Stromeko@nexgo.de> writes:
> François Pinard writes:
>> Org could tell Gnus that I am not really reading an article as if I was
>> using Gnus interactively.
> You keep saying that; while clearly you could coerce Gnus into doing
> something like that I'm not sure Gnus would entertain to listen to
> such a request. This is probably best asked on a Gnus mailing list,
> but it seems that Gnus wants to present search results in an ephemeral
> group. If you treat a link as a search that finds one article, then
> the problem you're trying to solve goes away, I'd think.
The whole discussion is about how Org mode should best follow "gnus:"
links. I surely do not mind if Org uses ephemeral groups or any other
kind of machinery. My only suggestion is that, whatever the mechanics,
Org following a "gnus:" link should manage so Gnus does not change the
article flags. If Org asks Gnus to perform a search to locate a given
article, it seems like overkill to me, but I may well be wrong and not
see the advantages.
François
next prev parent reply other threads:[~2014-01-08 1:37 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 [this message]
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=87mwj7w8xn.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).