From: Brian Sniffen <bts@evenmere.org>
To: David Bremner <david@tethera.net>,
David Belohrad <david@belohrad.ch>,
notmuch@notmuchmail.org
Subject: Re: i do not have INBOX
Date: Fri, 20 Jan 2017 10:48:07 -0500 [thread overview]
Message-ID: <8760l9u408.fsf@istari.evenmere.org> (raw)
In-Reply-To: <87lgu53no0.fsf@rocinante.cs.unb.ca>
David Bremner <david@tethera.net> writes:
> David Belohrad <david@belohrad.ch> writes:
>
>>
>> my directory does not contain INBOX, as inside the Maildir folder is
>> directly /cur, /new, /tmp. How do I search in this particular one?
>
> Quoting notmuch-search-terms(7)
>
> The exact syntax for maildir folders depends on your mail configura‐
> tion. For maildir++, folder:"" matches the inbox folder (which is the
> root in maildir++), other folder names always start with ".", and
> nested folders are separated by "."s, such as folder:.classes.topol‐
> ogy. For "file system" maildir, the inbox is typically folder:INBOX
> and nested folders are separated by slashes, such as
> folder:classes/topology.
>
>> The question is related to usage of 'afew' to move all mails which
>> have 'deleted' tag into Trash folder (which I have under .Trash)
>
> Hopefully the above is enough to help you formulate the right query.
> You probably also want the options --format=text0 and --output=files for
> notmuch search.
The next paragraph of that man page has an important warning for anyone
planning on re-arranging files based on the results of notmuch:
Both path: and folder: will find a message if any copy of that
message is in the specific directory/folder.
It's important to filter the names (e.g., `notmuch ...|grep -Fzv
/.|xargs -Ifoo mv foo $MAILDIR/.Trash/cur/`) before relying on them.
-Brian
next prev parent reply other threads:[~2017-01-20 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 11:11 i do not have INBOX David Belohrad
2017-01-20 12:45 ` David Bremner
2017-01-20 15:48 ` Brian Sniffen [this message]
2017-01-20 16:20 ` David Belohrad
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=8760l9u408.fsf@istari.evenmere.org \
--to=bts@evenmere.org \
--cc=david@belohrad.ch \
--cc=david@tethera.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).