Re: [notmuch] [PATCH (rebased)] Handle message renames in mail spool
On Fri, 2009-12-04 at 10:35 -0800, Carl Worth wrote: But the above sounds like the List-Id header is unreliable enough to be useless. FWIW, that does not match my experience. Any reason not to just use something like to:notm...@notmuchmail to match messages sent to a list like this one? I'd had much better luck matching List-Id than matching addresses in recent years. YMMV. Bdale ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
[notmuch] [PATCH 2/2] notmuch list: A new command to produce various lists.
On Thu, 2009-11-19 at 15:41 +0100, Carl Worth wrote: > The other reason I've wanted this is have something like a "folder view" > that would show a list of tags and a number of messages with each tag, > (or a number of messages with that tag and the inbox tag). > > I know that Keith said he'd prefer to use a view like that as his > primary way of reading mail. Yes. I've been pondering approaches to prioritizing the pool of unread messages. Most of my thinking so far is along the lines of the ability to automatically apply tags to new messages on various criteria combined with the ability to manipulate the order in which tags are presented in a view like what you're describing. For better or worse, with about 45k messages hitting my inbox per year *after* most of the list traffic gets peeled off and fed to a private NNTP server, it's not about reading all of my email any more... it's about finding and reading the stuff that actually matters *to me*. Can't tell you how excited I am about what's happening here! Bdale
[notmuch] 25 minutes load time with emacs -f notmuch
On Sat, 2009-11-21 at 15:51 +0100, Stefan Schmidt wrote: > Sadly that takes around 25 minutes here on an Intel Core2Duo notbeook > (Thinkpad > X200s). I tried this several times now. CPU load was low (~10%) during this > time > so it is mostly IO bound. I see the same behavior on my notebook. I gather from talking to keithp that things like the 'state of already being read' aren't being picked up from the file names in the local Maildir yet. Thus I suspect it's a fairly unusual / worst case scenario trying to start up with 178k (in my case) supposedly-unread messages tagged inbox. I haven't figured out how to quickly tag everything as already read or archived or whatever .. can someone who knows more about what's going on confirm my hypothesis and if so, suggest the best approach to getting to a happier state? Bdale
[notmuch] [PATCH 0/4] Make tags applied by 'notmuch new' configurable.
On Tue, 2009-11-24 at 23:10 +0100, Jan Janak wrote: > Instead of 'inbox' and 'unread', I configure > 'notmuch new' to add a new tag called 'new' (and only that one). This tag > marks newly added messages that haven't been properly tagged yet by my > auto-tagging scripts. Oh, brilliant! I like it. Bdale
[notmuch] Debian packaging
On Sun, 2009-11-29 at 08:55 -0500, Jameson Graef Rollins wrote: > As much as I would love to, at this point I'm not quite offering to > actually be maintainer of a notmuch Debian package. Actually, since Carl is a DD now, I've already nudged him about maintaining a Debian package, and offered to help. Perhaps your work will provide additional motivation. ;-) FWIW, it's entirely possible to configure git-buildpackage to package directly from the master branch. I do that with AltOS, details can be found in the fw/altos repo on git.gag.com if you're curious. There are various ways you could do this, but I've put a hook in .gbp.conf that invokes a new debian/rules 'prebuild' target... This allows me to just run 'git-buildpackage' any time we want fresh packages, and get a Debian changelog crafted from the git commit logs since the last time I built a Debian package. Bdale
[notmuch] reading with multiple MUAs from MailDir
On Thu, 2009-12-10 at 22:11 -0800, Dirk Hohndel wrote: > While playing with notmuch I am still using evolution to read the email > in the same MailDir that is being indexed / processed by notmuch. With > the result that lots of emails can not be found in notmuch if they have > been marked as read in evolution between processing in notmuch and > trying to access them from the user interface. > > This makes notmuch /really/ hard to test for me at this point. For what it's worth, this drives me nuts, too. Bdale
[notmuch] [PATCH (rebased)] Handle message renames in mail spool
On Fri, 2009-12-04 at 10:35 -0800, Carl Worth wrote: > But the above sounds like the List-Id header is unreliable enough to be > useless. FWIW, that does not match my experience. > Any reason not to just use something like > to:notmuch at notmuchmail to match messages sent to a list like this one? I'd had much better luck matching List-Id than matching addresses in recent years. YMMV. Bdale
[notmuch] [PATCH (rebased)] Handle message renames in mail spool
On Thu, 2009-12-17 at 06:01 +0600, Mikhail Gusarov wrote: > Twas brillig at 16:51:17 16.12.2009 UTC-07 when bdale at gag.com did gyre and > gimble: > > >> But the above sounds like the List-Id header is unreliable enough to > >> be useless. > > BG> FWIW, that does not match my experience. > > Yeah. This mail just arrived to my "main" folder instead of "notmuch" > one, as you kept me in CC and hence Mailman did not send the copy with > List-Id to me. > > Please read the whole thread. I did. I guess I've just been lucky enough to mostly participate in lists run with other software than Mailman or whose admins didn't leave this default behavior in place... [sigh] I will, very unhappily, concede the point. Bdale
