unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jameson Rollins <jrollins@finestructure.net>
To: Carl Worth <cworth@cworth.org>,
	Sebastian Spaeth <Sebastian@SSpaeth.de>,
	notmuch@notmuchmail.org
Subject: Re: Introducing notmuchsync
Date: Wed, 24 Feb 2010 13:49:44 -0500	[thread overview]
Message-ID: <87wry21nav.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87wry2wl7p.fsf@yoom.home.cworth.org>

[-- Attachment #1: Type: text/plain, Size: 1974 bytes --]

On Wed, 24 Feb 2010 10:19:06 -0800, Carl Worth <cworth@cworth.org> wrote:
> Elsewhere in the thread Jameson Rollins wrote:
> > I should have mentioned in my previous mail that I think this tool is
> > a great idea, and I plan on using it.  I just hope that all of it's
> > functionality will be integrated directly into notmuch itself.
> 
> I think that's the open question still. How much of this kind of
> functionality do we integrate into notmuch itself. I don't know the
> answer to that question yet, but I'm quite happy to see people
> experimenting with doing scripts like this on top of notmuch already.
> 
> I do know that I want to do thing to make such scripting easier,
> (independent of whether the current functionality gets folded into
> notmuch).

Hey, Carl.  Yeah, this was an old post and there's been lots of
discussion about it.  I'm certainly more flexible about my position now
than I think I was originally.

In fact, I actually gave up on syncing notmuch and maildir, and am
basically punting on maildir altogether.  This is slightly problematic
because notmuch is still missing some key features so I occasionally
have to use other mailers to achieve certain things (especially OpenPGP
stuff).  I worry about it down the line as well, if I ever have to use
another mailer for any reason.  All mail I've received since my switch
to notmuch will show up as "unread" in maildir readers.

I think notmuch wrapper scripts like notmuchsync are going to be crucial
for notmuch down the line, so I definitely agree that doing everything
possible to make it easier for them is a very good thing.  I am using
notmuchsync for deleting "delete" tagged messages, for which it's very
useful.  It's pretty slow, though, which I've been chalking up to the
fact that it has to parse the notmuch "show" output.  Once notmuch can
output just the paths to messages matching search results that should
get much much faster.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2010-02-24 18:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18 15:12 Introducing notmuchsync Sebastian Spaeth
2010-01-18 15:24 ` Sebastian Spaeth
2010-01-18 15:41 ` Michal Sojka
2010-01-18 15:57   ` Sebastian Spaeth
2010-01-19 13:37     ` Sebastian Spaeth
2010-01-19 15:00       ` Marten Veldthuis
2010-01-19 15:24         ` Jameson Rollins
2010-01-19 15:52           ` Sebastian Spaeth
2010-01-19 16:04             ` Jameson Rollins
2010-01-19 16:13               ` Sebastian Spaeth
2010-01-19 16:29               ` Servilio Afre Puentes
2010-01-19 16:38                 ` Jameson Rollins
2010-01-20  8:20               ` Tassilo Horn
2010-01-19 15:42         ` Sebastian Spaeth
2010-01-18 15:48 ` Marten Veldthuis
2010-02-24 18:19 ` Carl Worth
2010-02-24 18:49   ` Jameson Rollins [this message]
2010-02-25  9:50     ` Sebastian Spaeth
2010-02-25  9:40   ` Sebastian Spaeth
2010-03-01  8:57   ` Michal Sojka
2010-03-01 16:27     ` Ben Gamari
2010-03-01 17:18       ` Michal Sojka
2010-03-01 18:43         ` Ben Gamari
2010-03-01 20:20           ` Michal Sojka

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=87wry21nav.fsf@servo.finestructure.net \
    --to=jrollins@finestructure.net \
    --cc=Sebastian@SSpaeth.de \
    --cc=cworth@cworth.org \
    --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).