From: Ben Gamari <bgamari@gmail.com>
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: proposal for more streamlined mail flow in notmuch
Date: Mon, 25 Jan 2010 22:19:28 -0500 [thread overview]
Message-ID: <1264475514-sup-2878@ben-laptop> (raw)
In-Reply-To: <20100116204955.GA858@finestructure.net>
Excerpts from Jameson Rollins's message of Sat Jan 16 15:49:55 -0500 2010:
> To fascilitate this, two new functions should be implemented at the
> notmuch CLI level, so that things don't get fractured by different
> mail reader implementations:
>
> notmuch purge
>
> delete all 'delete' tagged messages, and/or execute "delete hooks"
>
> notmuch archive <search-terms>
>
> remove 'inbox' flags from messages and move messages an archive
> maildir, and/or execute "archive hooks"
>
I'm a little suspicious of this. Again, it seems like there is nothing
whatsoever preventing one from implementing this at a higher-level than
notmuch, which I believe should be little more than a thin-wrapper
around Xapian unless more functionality is absolutely necessary. I don't
understand why these sorts of proposals keep coming up when the above,
for example, could be easily implemented in a pair of ten line shell
scripts. Am I missing something?
In my opinion, the "fractured implementations" argument is mislead at
best. We currently have exactly two (in the case of vim, somewhat)
usable UIs. It's not difficult to see to it that they obey similar
conventions. If another UI pops up that fails to obey your favorite
convention, feel free to patch it. IMHO, it is not the place of notmuch
to force semantics onto the user (in fact, it tries to avoid this
wherever possible).
- Ben
prev parent reply other threads:[~2010-01-26 3:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 20:49 proposal for more streamlined mail flow in notmuch Jameson Rollins
2010-01-25 21:07 ` martin f krafft
2010-01-26 3:19 ` Ben Gamari [this message]
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=1264475514-sup-2878@ben-laptop \
--to=bgamari@gmail.com \
--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).