From: David Bremner <david@tethera.net>
To: Jean-Marc Liotier <jm@liotier.org>, notmuch@notmuchmail.org
Subject: Re: Alternative to no longer supported folder:foo* wildcard matching ?
Date: Tue, 10 Mar 2015 08:10:33 +0100 [thread overview]
Message-ID: <87a8zlxr86.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <54FE37F4.7090605@liotier.org>
Jean-Marc Liotier <jm@liotier.org> writes:
>
> % cd ~/Maildir
> % mkdir .NM_myTopLevelFolder
> % ln -rs .myTopLevelFolder* -t .NM_myTopLevelFolder
This is doing one level of links. If you want more hierarchy
you'll have to create subdirectories with links to only some of your
folders. In fact the NM_myTopLevelFolder doesn't seem useful to me,
since you don't gain any new queries that way.
So if you have .foo.* and .bar.*, I would
mkdir foo
ln -rs .foo.* -t foo
mkdir bar
ln -rs .bar.* -t bar
> On the downside:
> - It doubles the number of messages to index (though then even
> multiplied by two, my 300k messages are Not Much Mail™ - but still...)
Conceivably this has to do with duplicating the top level folder, not
sure; I don't see an increase. In particular I don't see in increase in
the output of "notmuch count", so in notmuch jargon, the number of
_messages_ does not increase but rather the number of _files_. There
will obviously be some growth in the database size, but there was
nothing too shocking in my experiments (I didn't measure carefully, but
my database is still at around 30% of the raw mail size)
> - myTopLevelFolder gets a NM_myTopLevelFolder twin and restricting the
> search scope to it requires using its twin's name
yes, I suppose that's true. But for "nice" symlink names this doesn't
seem so terrible. But *shrug* it's a matter of taste.
> - The additional messages are duplicates, so --remove-dups becomes
> mandatory in any search query
Based on the name, I'd suspect "remove-dups" corresponds roughly to the
default behaviour of notmuch in reporting results.
> - This method is good for restricting the search scope to a directory,
> but not for excluding a directory from the search scope... Which alas
> is what I desire most...
Either I don't understand what you want, or this might again be
something to do with notmuch-mutt. For me, queries like
notmuch count not 'path:list/**'
and
notmuch count not 'path:list/**' and from:bremner
work as expected.
Hope this helps,
d
next prev parent reply other threads:[~2015-03-10 7:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 19:55 Alternative to no longer supported folder:foo* wildcard matching ? Jean-Marc Liotier
2015-03-09 22:06 ` David Bremner
2015-03-10 0:16 ` Jean-Marc Liotier
2015-03-10 7:10 ` David Bremner [this message]
2015-03-10 12:21 ` Jean-Marc Liotier
2015-03-10 13:25 ` 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=87a8zlxr86.fsf@maritornes.cs.unb.ca \
--to=david@tethera.net \
--cc=jm@liotier.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).