From: David Bremner <david@tethera.net>
To: Greg Minshall <minshall@umich.edu>, notmuch@notmuchmail.org
Subject: Re: converting from nmh: how to?
Date: Mon, 05 Dec 2022 10:42:05 -0400 [thread overview]
Message-ID: <87h6y9kj42.fsf@tethera.net> (raw)
In-Reply-To: <778714.1670213178@archlinux>
Greg Minshall <minshall@umich.edu> writes:
> hi. apologies if this is an FAQ.
>
> i'm exploring notmuch (via the emacs front-end). i have 1.2M e-mail
> messages sorted into 200 or so nmh folders. (*)
>
> after running `notmuch new`, i end up with 1.2M "unread" messages, all
> in "inbox".
>
> i would like to end up with the "inbox" tag applied only to messages
> actually in my nmh +inbox folder; messages from *other* nmh folders
> should end up with a tag derived from that folder name.
If I remember how mh works you should be able to use something like
notmuch tag -inbox '*'
notmuch tag +inbox path:relative/path/to/inbox/folder
you may want to use "notmuch dump > backup.tags" before some bold experiments.
> and, i would like to have the "unread" tag only apply to messages that
> nmh thinks are unseen.
>
> (iiuc, nmh keeps track of unseen messages in ".mh_sequences" local to
> each nmh folder; i don't think i care about any other sequences,
> including "cur", in any of the ".mh_sequences" files.)
>
> is there a known procedure for accomplishing this? or, thoughts on
> same?
notmuch does not index filenames, so that makes things a bit more
challenging. With a little scripting, you could extract the message-id
for message 'n' and pass that to notmuch. I'd probably write a python
script (and use the 'notmuch2' module), but it's doable as a shell
script also (given some hack to extract the message-id).
next prev parent reply other threads:[~2022-12-05 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 4:06 converting from nmh: how to? Greg Minshall
2022-12-05 8:10 ` inwit
2022-12-05 13:54 ` Greg Minshall
2022-12-05 14:42 ` David Bremner [this message]
2022-12-06 0:59 ` Greg Minshall
2022-12-06 1:11 ` David Bremner
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=87h6y9kj42.fsf@tethera.net \
--to=david@tethera.net \
--cc=minshall@umich.edu \
--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).