From: Mark Anderson <MarkR.Anderson@amd.com>
To: "Antoine Beaupré" <anarcat@anarcat.ath.cx>,
"Jameson Graef Rollins" <jrollins@finestructure.net>,
"Jacek Generowicz" <jacek.generowicz@cern.ch>,
notmuch@notmuchmail.org
Subject: Re: Message deletion wisdom
Date: Fri, 6 Apr 2012 14:17:50 -0600 [thread overview]
Message-ID: <3wdobr4vclt.fsf@testarossa.amd.com> (raw)
In-Reply-To: <87k41ucfqc.fsf@marcos.anarcat.ath.cx>
On Thu, 5 Apr 2012 12:20:43 -0400, Antoine Beaupré <anarcat@anarcat.ath.cx> wrote:
> Finally, I want to voice that I feel a "delete" key, even if it doesn't
> delete mails, seems like an important part of a mail user
> agent. Archiving mail is one thing, but for the love and respect of
> sysadmins and the infrastructure they maintain, please consider adding
> at least a way to *tag* those deleted emails.
>
> Having the above keys being defined as standard in notmuch don't seem
> like much to ask.
>
> This may be a dissenting view here, but your mail is not that
> important. :P
Hear! Hear!
I also would like to have some natural way to mark things as "I never
expect to look at this again". Do I really need to keep track of every
vacation and calendar notice? Or every logfile I have my infrastructure
email to me, that doesn't really need to be in email, but was easily
shoehorned into the existing notification/logging side effects of mail?
My infrastructure is building new models for unit-level testing daily, I
don't need to keep track of every model for years, and I have been using
notmuch for years. Hmm, December 2009, it has been a while. :)
I do set up a deleted tag for my own use, but it would be nice if that
were viewed as a little more natural use case by the software from the
./configure script. Yes Virginia, notmuch comes with NotMuch of a box.
Thanks,
-Mark
next prev parent reply other threads:[~2012-04-06 20:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 10:37 Message deletion wisdom Jacek Generowicz
2012-04-03 23:32 ` Jameson Graef Rollins
2012-04-04 7:38 ` Jani Nikula
2012-04-05 16:24 ` Antoine Beaupré
2012-04-05 16:20 ` Antoine Beaupré
2012-04-06 20:17 ` Mark Anderson [this message]
2012-04-09 21:36 ` green
2012-04-08 22:24 ` Sebastian Spaeth
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3wdobr4vclt.fsf@testarossa.amd.com \
--to=markr.anderson@amd.com \
--cc=anarcat@anarcat.ath.cx \
--cc=jacek.generowicz@cern.ch \
--cc=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).