From: Wes Hardaker <wes@hardakers.net>
To: ding@gnus.org
Subject: Re: Possible ideas for "inbox zero"
Date: Mon, 14 Dec 2015 14:09:43 -0800 [thread overview]
Message-ID: <0lr3iowul4.fsf@wjh.hardakers.net> (raw)
In-Reply-To: <m3y4cxhrc8.fsf@gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 14 Dec 2015 18:28:55 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> This article has some workable ideas for a more "inbox zero" kind of
> setup:
I've long thought about how to achieve a reduced view of my boxes. I
think my biggest problem stems from a number of elements, that could
easily be implemented with some software tweaks. My mail falls into a
few simple categories in general:
a) Reply/Act immediately and delete (wish they were all this way)
b) Reply/Act immediately but then keep the thread around for further study
until it dies. This is a hard one (more below).
bb) read immediately and keep it around until it dies or I need to
reply to a sub-thread
c) Can't reply/act right now because of either time or some dependency issue
d) delete it because it doesn't need a response (even better than a!)
e) archive for later for reference
The problem is that most of my mail falls into the dreaded b category or
bb category. Sometimes the b/bb category eventually needs to moved to
archive but I don't know that yet either.
I use some marks to help with this, and have a script that I run
directly on the imap server to delete trashed mail only after a
particular life cycle (eg, 21 days). So the folder appears mostly
blank. But I rarely seem to mentally trust it and thus leave stuff
marked as read instead of trashed (I also have a script that runs out of
cron syncing Trashed (phone) and Expired (gnus)).
The bulk of my inbox(es - 10 fairly important ones) fall into the large
category filled with past b and bb type articles. Occasionally I try to
take a run through them and clean them up.
One idea: have a mark for a subject that functionally says "leave around
till it's silent for a week, then hide it for another week, then trash
it".
I also have an "old" version of most boxes that serve as a fade-out
point, but again: it's hard to do searching with a combined view
(notmuch really helps here, except I don't mirror the old boxes from my
imap server because of the doubled bandwidth problem of pulling it down
again into a different box once it's auto-moved via script on the
server).
Ugh. No one is still reading this I'm sure.
--
Wes Hardaker
My Pictures: http://capturedonearth.com/
My Thoughts: http://blog.capturedonearth.com/
next prev parent reply other threads:[~2015-12-14 22:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 17:28 Lars Magne Ingebrigtsen
2015-12-14 22:09 ` Wes Hardaker [this message]
2015-12-14 22:26 ` Dan Christensen
2015-12-14 22:52 ` Xavier Maillard
2015-12-15 17:35 ` Nikolaus Rath
2015-12-14 22:54 ` Lars Magne Ingebrigtsen
2015-12-14 22:10 ` Dan Christensen
2015-12-14 22:48 ` Lars Magne Ingebrigtsen
2015-12-14 23:05 ` Adam Sjøgren
2015-12-15 14:58 ` training spam filter (was: Possible ideas for "inbox zero") Peter Münster
2015-12-15 17:17 ` training spam filter Dan Christensen
2015-12-15 19:44 ` Adam Sjøgren
2016-03-07 13:58 ` Ted Zlatanov
2016-03-07 14:11 ` Adam Sjøgren
2016-03-07 15:10 ` Ted Zlatanov
2016-03-07 16:36 ` Adam Sjøgren
2015-12-14 22:27 ` Possible ideas for "inbox zero" Xavier Maillard
2015-12-14 23:02 ` Adam Sjøgren
2015-12-14 23:24 ` Adam Sjøgren
2015-12-15 7:52 ` Russ Allbery
2015-12-15 14:55 ` Adam Sjøgren
2015-12-15 18:40 ` Russ Allbery
2015-12-20 0:36 ` Tim Landscheidt
2015-12-25 4:01 ` Tim Landscheidt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0lr3iowul4.fsf@wjh.hardakers.net \
--to=wes@hardakers.net \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).