From: Matt Lundin <mdl@imapmail.org>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: Keith Lancaster <klancaster1957@acm.org>,
Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [OT] Emacs for email?
Date: Wed, 02 Dec 2009 14:03:55 -0500 [thread overview]
Message-ID: <m2ocmhmc4k.fsf@fastmail.fm> (raw)
In-Reply-To: <878wdlh2sr.wl%ucecesf@ucl.ac.uk> (Eric S. Fraga's message of "Wed, 02 Dec 2009 14:24:20 +0000")
Eric S Fraga <ucecesf@ucl.ac.uk> writes:
> At Wed, 02 Dec 2009 12:01:38 +0100,
> jemarch@gnu.org wrote:
>> I've moved to a "0 size mailbox" approach to handling my email
>> (which works well with org and, in fact, requires org to work at
>> all really) so this is not an issue for me.
>>
>> That sounds like an interesting approach. Could you elaborate on
>> that? Yes, I also have problems with my huge longstanding mailboxes
>> :(
>
> The aim is to not have to go back to your inbox to see what you have
> to deal with -- that's what org-mode (or whatever) is for. Too much
> time is wasted trawling through huge inboxes looking for actions to
> respond to which means you're using an inbox as a todo list. This is
> not effective.
As an aside, this is precisely why I like Gnus so much. By default, read
messages are hidden -- so it makes it easy to get down to "zero" without
having to refile, archive, or delete anything. Automatic
archiving/expiry takes care of the problem of overly large mailboxes.
- Matt
next prev parent reply other threads:[~2009-12-02 19:04 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 21:34 [OT] Emacs for email? Keith Lancaster
2009-12-01 22:59 ` Ben Finney
2009-12-02 7:59 ` Tassilo Horn
2009-12-02 8:31 ` Ben Finney
2009-12-02 9:23 ` bluedian
2009-12-01 23:28 ` David Bremner
2009-12-01 23:36 ` Nick Dokos
2009-12-01 23:57 ` Darlan Cavalcante Moreira
2009-12-02 0:39 ` Keith Lancaster
2009-12-02 14:22 ` Leo
2009-12-02 18:38 ` David Neu
2009-12-02 22:48 ` Eric Schulte
2009-12-02 23:08 ` Keith Lancaster
2009-12-03 5:21 ` Rémi Vanicat
2009-12-02 13:43 ` Matt Price
2009-12-02 21:04 ` David Maus
2009-12-03 16:53 ` Matt Price
2009-12-03 21:55 ` Darlan Cavalcante Moreira
2009-12-02 0:40 ` Matt Lundin
2009-12-02 1:02 ` Henri-Paul Indiogine
2009-12-02 8:03 ` Tassilo Horn
2009-12-02 2:15 ` Dan Davison
2009-12-02 2:56 ` Russell Adams
2009-12-02 6:36 ` Manuel Hermenegildo
2009-12-02 6:39 ` Gour
2009-12-03 7:05 ` Russell Adams
2009-12-03 6:38 ` Rémi Vanicat
2009-12-03 8:22 ` Ulf Stegemann
2009-12-03 11:25 ` Matt Lundin
2009-12-03 10:53 ` Bernt Hansen
2009-12-02 6:30 ` Xavier Maillard
2009-12-02 9:37 ` Eric S Fraga
2009-12-02 11:01 ` jemarch
2009-12-02 14:24 ` Eric S Fraga
2009-12-02 16:31 ` jemarch
2009-12-02 20:30 ` David Maus
2009-12-02 17:31 ` Rémi Vanicat
2009-12-02 18:33 ` Eric Schulte
2009-12-02 19:03 ` Matt Lundin [this message]
2009-12-02 17:00 ` Russell Adams
2009-12-02 12:58 ` Otto Diesenbacher
2009-12-03 17:10 ` Henri-Paul Indiogine
2009-12-03 17:51 ` Matt Lundin
2009-12-03 19:53 ` Enrico Indiogine
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=m2ocmhmc4k.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=klancaster1957@acm.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).