From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Re: gnus: link annoyance
Date: Tue, 07 Jan 2014 09:34:57 -0500 [thread overview]
Message-ID: <87a9f7eu7i.fsf@iro.umontreal.ca> (raw)
In-Reply-To: <877gac3pze.fsf@gmx.us> (rasmus@gmx.us's message of "Tue, 07 Jan 2014 14:01:41 +0100")
Rasmus <rasmus@gmx.us> writes:
> Say you have a mail X that's semi-interesting. Do you then, read it,
> mark it as unread, close the buffer, go back later, read it again and
> unread it?
I once used Gnus as a reader who tremendously helped me at handling the
high email volume of email I got when I maintained many GNU packages
(the Translation Project and also "tar" were pretty generative!) and
following lots of newsgroups. Now that I got out of maintenance, Gnus
as a mail reader is a bit of overkill, but I still use it to peruse
archives I collected on many subjects, in about a thousand of nnfolders.
Searching them all is often convenient. Normally, I only delete
articles from one of these archives when I decide to ponder it whole and
clean it up, and then read articles one after another the normal Gnus
way. Otherwise, I prefer them untouched even if casually consulted,
postponing the cleanup until I get motivation and a good chunk of time.
For the detail, when not in clean mode, I often unread an article just
after having read it, or when I know I am perusing a lot, just let them
read but quit by "Q" instead of "q", which reverts all the marks.
From an hits buffer generated by org-grep, I can get many hits of many
kinds (Org, non-Org, mailboxes or mailgroups), and while checking many
of these links in speedy mode, it slows me down considerably if I have
to stay alert and careful at unreading Gnus articles among the rest, and
fairly dangerous if I get tired and stop being careful.
François
next prev parent reply other threads:[~2014-01-07 14:35 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
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 [this message]
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=87a9f7eu7i.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).