From: Anthony Towns <aj@erisian.com.au>
To: Jameson Rollins <jrollins@finestructure.net>
Cc: notmuch@notmuchmail.org
Subject: Re: Plans for the 0.2 release (this week)
Date: Fri, 9 Apr 2010 13:22:51 +1000 [thread overview]
Message-ID: <x2u87b3a4191004082022n98887647lef9b04daf7c50943@mail.gmail.com> (raw)
In-Reply-To: <87tyrmavoc.fsf@servo.finestructure.net>
On Fri, Apr 9, 2010 at 00:03, Jameson Rollins
<jrollins@finestructure.net> wrote:
> Presumably others must be annoyed about having to manually "read" and
> archive all their sent mail, unless there's some other way that people
> having been dealing with this that I'm not aware of.
I haven't switched over to notmuch properly yet, but in my initial
import of my mail I made a couple of patches to notmuch new that let
me get the tags right first. One was to make:
notmuch new --initial-tags=list,unread
set the initial tags for newly found messages to "list" and "unread"
instead of the default "inbox" and "unread".
The other was to make:
find Mail/.Saved/ -type f | notmuch new --initial-tags=archived --file-list
only process the mail files listed on stdin (via find), and give them
the explicit tags I specify. That way I could import all my existing
archived mail without it appearing in my inbox or as unread.
Unfortunately the second one ended up complicated and a bit slow (I
think because I'm doing a talloc() for every line on stdin, and
talloc_free() by context every time the base directory changes; that
sort of behaviour was necessary in order to do duplicate checking in a
sane way)
But anyway, that would let you do:
find Mail/.Drafts/ -type f | notmuch new --initial-tags=draft --file-list
notmuch new
to get drafts correctly tagged.
(I don't have the patches handy at the moment; but can certainly dig
them up if there's interest)
Cheers,
aj
--
Anthony Towns <aj@erisian.com.au>
next prev parent reply other threads:[~2010-04-09 3:22 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 22:12 Plans for the 0.2 release (this week) Carl Worth
2010-04-07 22:23 ` James Westby
2010-04-08 14:34 ` Mike Kelly
2010-04-12 18:27 ` Mike Kelly
2010-04-08 7:47 ` Sebastian Spaeth
2010-04-08 12:21 ` Anthony Towns
2010-04-13 16:02 ` Carl Worth
2010-04-08 8:13 ` David Edmondson
2010-04-08 14:54 ` Dirk Hohndel
2010-04-08 13:52 ` Jameson Rollins
2010-04-08 14:55 ` Dirk Hohndel
2010-04-13 16:06 ` Carl Worth
2010-04-08 14:03 ` Jameson Rollins
2010-04-08 14:58 ` Dirk Hohndel
2010-04-08 15:21 ` Michal Sojka
2010-04-08 15:57 ` draft handling [was: Re: Plans for the 0.2 release (this week)] Jameson Rollins
2010-04-08 21:28 ` Plans for the 0.2 release (this week) Carl Worth
2010-04-08 21:38 ` Jameson Rollins
2010-04-09 0:22 ` Mike Kelly
2010-04-08 15:30 ` Mike Kelly
2010-04-09 3:22 ` Anthony Towns [this message]
2010-04-09 4:25 ` Michal Sojka
2010-04-09 16:21 ` micah anderson
2010-04-08 14:22 ` Michal Sojka
2010-04-09 4:32 ` Michal Sojka
2010-04-09 7:35 ` Sebastian Spaeth
2010-04-09 17:14 ` Dirk Hohndel
2010-04-10 3:06 ` Carl n∅tmuch 䚳 Worth
2010-04-10 4:44 ` Dirk Hohndel
2010-04-10 4:47 ` Dirk Hohndel
2010-04-10 13:05 ` Jameson Rollins
2010-04-10 14:39 ` Dirk Hohndel
2010-04-10 9:02 ` Michal Sojka
2010-04-10 13:06 ` Jameson Rollins
2010-04-10 13:09 ` Jameson Rollins
2010-04-10 14:06 ` Michael Elkins
2010-04-10 19:58 ` Michal Sojka
2010-04-10 13:52 ` Sebastian Spaeth
2010-04-10 13:56 ` Jameson Rollins
2010-04-10 14:41 ` Dirk Hohndel
2010-04-13 17:20 ` Carl Worth
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=x2u87b3a4191004082022n98887647lef9b04daf7c50943@mail.gmail.com \
--to=aj@erisian.com.au \
--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).