<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.mail.notmuch.general">
    <title>gmane.mail.notmuch.general</title>
    <link>http://blog.gmane.org/gmane.mail.notmuch.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/15019"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/15014"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/15012"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/15009"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/15002"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/14998"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/14987"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/14986"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/14985"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/14984"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/14963"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/14962"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/14961"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/14950"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/14946"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/14931"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/14920"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/14918"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/14915"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.mail.notmuch.general/14910"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/15019">
    <title>[PATCH] devel: add dkg's printmimestructure script to notmuch develscripts</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/15019</link>
    <description>&lt;pre&gt;From: David Bremner &amp;lt;bremner&amp;lt; at &amp;gt;debian.org&amp;gt;

I find this script pretty useful when figuring out who to blame for
MIME rendering problems.  It currently isn't very widely known, so it
seems worth distributing with notmuch.
---

I did a small amount whitespace cleanup compared to version in dkg's git repo.

 devel/printmimestructure | 54 ++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 54 insertions(+)
 create mode 100755 devel/printmimestructure

diff --git a/devel/printmimestructure b/devel/printmimestructure
new file mode 100755
index 0000000..b8084a9
--- /dev/null
+++ b/devel/printmimestructure
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -0,0 +1,54 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
+#!/usr/bin/env python
+# -*- coding: utf-8 -*-
+
+# Author: Daniel Kahn Gillmor &amp;lt;dkg&amp;lt; at &amp;gt;fifthhorseman.net&amp;gt;
+# License: GPLv3+
+
+# Updates: git://lair.fifthhorseman.net/~dkg/printmimestructure
+
+# This script reads a MIME message from stdin and produces a treelike
+# representation on it stdout.
+
+# Example:
+#
+# 0 dkg&amp;lt; at &amp;gt;alice:~$ printmimestructure &amp;lt; 'Maildir/cur/1269025522.M338697P1202&lt;/pre&gt;</description>
    <dc:creator>david-1j+SLnlVNwXR7s880joybQ&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2013-05-20T15:59:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/15014">
    <title>Python Bindings missing on PyPI</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/15014</link>
    <description>&lt;pre&gt;Hi,

I noticed that the python bindings of notmuch are not available via pypi.
It seems that in the past something was registered but is not any longer.

Without the bindings, it is not possible to use python packages that
depend on notmuch within virtualenv. Virtualenv is a widely used app
to run python programs in an isolated environment.

Is there any rationale that prevents registering the python bindings
on pypi?
If this is only because of missing maintainer, would anybody
object if I put the bindings on pypi?
If nobody objects, I as the creator, would have admin permissions to
the pypi entry. I don't hoard these rights, if anybody else wants
access, please tell me your pypi username. Bus factors of 1 are
terrible.

Thanks and best regards,

        Patrick
&lt;/pre&gt;</description>
    <dc:creator>Patrick Gerken</dc:creator>
    <dc:date>2013-05-20T14:14:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/15012">
    <title>how the date query works?</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/15012</link>
    <description>&lt;pre&gt;Dear all,

could someone explain how to use date query? As of Oct 2012 Jani added
set of patches doing date query.

When I open in emacs search, and I type 'date:today', some output
appears, but not the one I would expect.

Interesting enough is, that if I press 'da' and then &amp;lt;tab&amp;gt;, it offers
date search.

Is there any kind of manual how to use it? I'm of course particularly
interested in 'today', 'yesterday', 'last week', 'last month' :)

thanks

david

&lt;/pre&gt;</description>
    <dc:creator>David Belohrad</dc:creator>
    <dc:date>2013-05-20T13:33:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/15009">
    <title>[PATCH 0/2] ruby: general improvements</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/15009</link>
    <description>&lt;pre&gt;Hi,

Not much to say here.

Felipe Contreras (2):
  ruby: use in-tree notmuch library
  ruby: fix missing symbol UINT2FIX()

 bindings/ruby/extconf.rb | 23 ++++++++++++++++++++---
 bindings/ruby/query.c    |  2 +-
 2 files changed, 21 insertions(+), 4 deletions(-)

&lt;/pre&gt;</description>
    <dc:creator>Felipe Contreras</dc:creator>
    <dc:date>2013-05-20T12:24:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/15002">
    <title>use of flet in notmuch-emacs</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/15002</link>
    <description>&lt;pre&gt;
Today I noticed

,----
| emacs --quick --directory emacs -batch -f batch-byte-compile emacs/notmuch-show.el
| 
| In notmuch-show-view-part:
| emacs/notmuch-show.el:541:22:Warning: `flet' is an obsolete macro (as of
|     24.3); use either `cl-flet' or `cl-letf'.
`----

Chatter on #emacs suggests that cl-flet is not in fact a replacement for
our use case since it does not do dynamic binding. I'm not really 100%
sure what the best plan is, but the old definition of flet is available
at

        https://github.com/sigma/el-x/blob/master/lisp/dflet.el

d


&lt;/pre&gt;</description>
    <dc:creator>David Bremner</dc:creator>
    <dc:date>2013-05-19T11:31:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/14998">
    <title>[PATCH 1/1] NEWS: removal of backported support for Emacs version 22</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/14998</link>
    <description>&lt;pre&gt;---
 NEWS | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/NEWS b/NEWS
index c348068..8d22e1b 100644
--- a/NEWS
+++ b/NEWS
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -18,6 +18,19 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; Bash command-line completion
   `notmuch config`. The new completion support depends on the
   bash-completion package.
 
+Emacs Interface
+---------------
+
+Removal of backported Emacs version 23 functionality for Emacs 22
+
+  Two years ago some Emacs 23 functionality that notmuch used were
+  backported to notmuch to be conditionally used with Emacs version 22.
+  That worked for a few months until new Emacs 23 features were taken
+  into use and due to lack of interest no one continued to backport
+  those. To clean up dead code and to avoid confusion in new
+  developers these backports are now removed.
+
+
 Vim Front-End
 -------------
 
&lt;/pre&gt;</description>
    <dc:creator>Tomi Ollila</dc:creator>
    <dc:date>2013-05-18T15:41:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/14987">
    <title>[PATCH 0/5] Make Emacs search use sexp format</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/14987</link>
    <description>&lt;pre&gt;This series implements an incremental S-expression parser and switches
search over to it.  To simplify things, it also implements better
handing of stderr for asynchronous processes so we don't have to
handle errors embedded in the S-expression stream.

&lt;/pre&gt;</description>
    <dc:creator>Austin Clements</dc:creator>
    <dc:date>2013-05-18T04:31:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/14986">
    <title>[PATCH] emacs: Proper error string handling in search sentinel</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/14986</link>
    <description>&lt;pre&gt;Apparently Emacs provides a function to stringify errors properly.
Use this in the search sentinel where we have to do our own error
messaging, rather than assuming the first error argument will be the
descriptive string.
---
 emacs/notmuch.el |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/emacs/notmuch.el b/emacs/notmuch.el
index e58c51d..4c1a6ca 100644
--- a/emacs/notmuch.el
+++ b/emacs/notmuch.el
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -660,7 +660,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; of the result."
       ;; things happen if a sentinel signals.  Mimic
       ;; the top-level's handling of error messages.
       (error
-       (message "%s" (second err))
+       (message "%s" (error-message-string err))
        (throw 'return nil)))
     (if (and atbob
      (not (string= notmuch-search-target-thread "found")))
&lt;/pre&gt;</description>
    <dc:creator>Austin Clements</dc:creator>
    <dc:date>2013-05-17T20:14:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/14985">
    <title>[PATCH] emacs: Fix trimming regexp in notmuch-check-exit-status</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/14985</link>
    <description>&lt;pre&gt;For such a simple regexp, this was broken in a very complicated way.

The intent was to strip the newline (and potentially other whitespace)
off the end of the error string so there wasn't an extra newline in
the error signal.  However, the regexp was deeply dependent on the
active syntax table and the subtleties of $.  We didn't notice this
because all notmuch major modes put ?\n in the whitespace class, which
makes this behaved as intended: the "\\s " matches all newlines, but
by matching the newline character, causes the $ *not* to match
*except* where it matched the empty string at the very end of the
string, which was not followed by a newline.

However, if the syntax table declares ?\n to be non-whitespace
(lisp-mode declares it as endcomment, and is likely to be the mode
you're in when testing functions), then this regexp behaves completely
differently, matching trailing spaces at the end of every line within
the string.

The solution is to say what we mean for whitespace *and* to switch
from $ to \',&lt;/pre&gt;</description>
    <dc:creator>Austin Clements</dc:creator>
    <dc:date>2013-05-17T20:14:03</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/14984">
    <title>[PATCH] emacs: Compute build dependencies to fix byte compile issues</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/14984</link>
    <description>&lt;pre&gt;Previously, we simply byte compiled each Elisp source file
independently.  This is actually the wrong thing to do and can lead to
issues with macros and performance issues with substitutions because
1) when the byte compiler encounters a (require 'x) form, it will load
x.elc in preference to x.el, even if x.el is newer, and as a result
may load old macro and substitution definitions and 2) if we update a
macro or substitution definition in one file, we currently won't
re-compile other files that depend on the file containing the
definition.

This patch addresses these problems by computing make dependency rules
from the (require 'x) forms in the Elisp source files, which we inject
into make's dependency database.
---
 emacs/Makefile.local |   12 +++++++++
 emacs/make-deps.el   |   66 ++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 78 insertions(+)
 create mode 100644 emacs/make-deps.el

diff --git a/emacs/Makefile.local b/emacs/Makefile.local
index fb82247..456700a 100644
--- a/emacs/Mak&lt;/pre&gt;</description>
    <dc:creator>Austin Clements</dc:creator>
    <dc:date>2013-05-17T20:13:31</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/14963">
    <title>simplify and fix performance tests</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/14963</link>
    <description>&lt;pre&gt;Jani noticed the alleged file notmuch-memory-test was missing.
Austin grumbled about explicitly adding tests to a list.
This series should give them both something else to grumble about.
 
&lt;/pre&gt;</description>
    <dc:creator>david-1j+SLnlVNwXR7s880joybQ&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2013-05-15T11:02:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/14962">
    <title>[PATCH] build: fix out-of-tree builds</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/14962</link>
    <description>&lt;pre&gt;Support for out-of-tree builds was added in
commit 3e4a9d60a9419621b08c647a306843d76c47c2cb
Author: Carl Worth &amp;lt;cworth-4HiWtcSh4w0dnm+yROfE0A&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
Date:   Wed Mar 9 15:02:42 2011 -0800

    build: Add support for non-source-directory builds.

and broken in
commit 7beeb8c88a014ecbc53d8241f10683b3c4c16228
Author: David Bremner &amp;lt;bremner-8fiUuRrzOP0dnm+yROfE0A&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
Date:   Sat Nov 17 12:28:15 2012 -0400

    test: initial performance testing infrastructure

Fix the build breakage.

Out-of-tree 'make test' has been broken since earlier than the above,
and remains broken, as does out-of-tree perf test, but at least the
build now works.

---

I didn't have the time to dig into the test and perf test breakage.
---
 Makefile                        |    3 +--
 performance-test/Makefile.local |    2 +-
 2 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/Makefile b/Makefile
index 73a8554..3301d30 100644
--- a/Makefile
+++ b/Makefile
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -3,8 +3,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 all:
 
 # List all subdirectories&lt;/pre&gt;</description>
    <dc:creator>Jani Nikula</dc:creator>
    <dc:date>2013-05-15T10:58:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/14961">
    <title>[PATCH] emacs: tag: fix compile warning</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/14961</link>
    <description>&lt;pre&gt;When compiling notmuch-tag.el there is a compile warning:
notmuch-tag.el:27:1:Warning: cl package required at runtime

Since we have decided to allow runtime use of cl we suppress this
warning by adding a tail comment to the file.
---

This warning has irritated me for some time: thanks to Austin (on irc)
for pointing out how to fix it.

Best wishes

Mark

 emacs/notmuch-tag.el |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/emacs/notmuch-tag.el b/emacs/notmuch-tag.el
index 75a438b..064cfa8 100644
--- a/emacs/notmuch-tag.el
+++ b/emacs/notmuch-tag.el
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -292,3 +292,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; begin with a \"+\" or a \"-\". If REVERSE is non-nil, replace all
 ;;
 
 (provide 'notmuch-tag)
+
+;; Local Variables:
+;; byte-compile-warnings: (not cl-functions)
+;; End:
&lt;/pre&gt;</description>
    <dc:creator>Mark Walters</dc:creator>
    <dc:date>2013-05-14T08:13:53</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/14950">
    <title>[PATCH 0/6] cli: better tooling support for duplicate messages</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/14950</link>
    <description>&lt;pre&gt;Patches 1-3 are an answer to a question on IRC:

&amp;lt;ccxCZ&amp;gt; is there a way for notmuch search --output=files to only output
        one file for Message-ID instead of all?

Yes, use --duplicate=0 on the command line. ;)

I suggest this interface (instead of, say, --output=file1 which was also
contemplated) for two reasons: it allows one to choose also other files
than the first one, and the same interface could be used later on in
notmuch show to display the duplicates.

An alternative could be something like --duplicates=(all|first|rest)
which would lack the possibility to pick a specific duplicate, but would
allow one to list all the "redundant" files with --duplicates=rest (this
would correspond to a number of invocations with --duplicate=1,
--duplicate=2, etc.)

Patches 4-6 add support for querying the file counts in notmuch
count. Most useful with a single id:&amp;lt;message-id&amp;gt; query I presume.


BR,
Jani.


Jani Nikula (6):
  cli: add --duplicate=N option to notmuch search
  test: test notmuch search --duplicat&lt;/pre&gt;</description>
    <dc:creator>Jani Nikula</dc:creator>
    <dc:date>2013-05-13T18:26:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/14946">
    <title>Joining messages into threads</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/14946</link>
    <description>&lt;pre&gt;Hi,

I am getting mails from some automated tools (let's imagine bugzilla for
example), which concern several specific topics (like bugs).
Unfortunately those mails are not 'threaded' (don't have In-Reply-To
header). Once the mails are indexed, is there a way make them threaded?
I don't think that just editing the mail file and running 'notmuch new'
would find out.

Similar question would be, can I join two separate message threads into
one by making the 'head' of one thread to be 'child' of the other
thread?

Thank you
&lt;/pre&gt;</description>
    <dc:creator>Vladimir Marek</dc:creator>
    <dc:date>2013-05-13T09:16:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/14931">
    <title>[PATCH 0/3] Allow widen reply</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/14931</link>
    <description>&lt;pre&gt;This is an initial draft of a patch to allow the emacs frontend to
"widen" the reply: i.e., change the headers to reply-to-all after a
reply-to-sender has been started.

The reply cli json output is modified to always output the
reply-to-all headers.

Emacs message mode already as a key binding for widening reply (C-c
C-f w) so we use that.

There are some things that need to be worked out: do we want to allow
narrowing the reply (ie going from reply-to-all back to
reply-to-sender)? I did not implement this as it was slightly easier
not to, message-mode doesn't have this by default, and it's easy for a
user to remove recipients.

I have not updated tests (the reply json test fails) or the
schemata. I thought it was worth deciding what format we wanted for
the json first.

Finally, I am not sure I have got the overriding of
message-widen-reply keybinding right. It does seem to work.

Best wishes

Mark



Mark Walters (3):
  cli: show: separate out the printing of recipient headers
  cli: reply: additionally o&lt;/pre&gt;</description>
    <dc:creator>Mark Walters</dc:creator>
    <dc:date>2013-05-11T20:15:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/14920">
    <title>[PATCH v2 0/8] search --exclude=all</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/14920</link>
    <description>&lt;pre&gt;This is a rebased version of
id:1340198947-29370-1-git-send-email-novalazy-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org I have not
tested it significantly in this form but the rebasing looks ok and all
the tests pass.

Best wishes

Mark




Mark Walters (2):
  lib: add --exclude=all option
  cli: add --exclude=all option to notmuch-search.c

Peter Wang (6):
  test: add tests for search --exclude=all
  man: clarify search --exclude documentation
  man: clarify search --exclude=flag
  man: document search --exclude=all
  lib: add NOTMUCH_EXCLUDE_FLAG to notmuch_exclude_t
  cli: use notmuch_exclude_t in option parser

 lib/notmuch-private.h     |    1 +
 lib/notmuch.h             |   23 ++++++++++++++++-------
 lib/query.cc              |   14 +++++++++-----
 lib/thread.cc             |   41 ++++++++++++++++++++++++++++++-----------
 man/man1/notmuch-search.1 |   29 +++++++++++++++++++++++------
 notmuch-search.c          |   24 +++++++++---------------
 test/excludes             |   22 ++++++++++++++++++++++
 7 fil&lt;/pre&gt;</description>
    <dc:creator>Mark Walters</dc:creator>
    <dc:date>2013-05-11T19:50:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/14918">
    <title>Xapian recovery after kernel oops</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/14918</link>
    <description>&lt;pre&gt;My laptop had a kernel oops this morning, apparently triggered by
getting bumped (not very hard, actually).  Upon restarting, I have a
corrupt database:

  $ notmuch search tag:inbox                                                                                                                                 
  A Xapian exception occurred opening database: The revision being read has been discarded - you should call Xapian::Database::reopen() and retry the operation

This is with Linux 3.8.11 and btrfs, though nothing else on the file
systems appears to have been affected.

  $ xapian-check Mail/.notmuch/xapian/
  Database couldn't be opened for reading: DatabaseModifiedError: The revision being read has been discarded - you should call Xapian::Database::reopen() and retry the operation
  Continuing check anyway
  Cross-checking document lengths between the postlist and termlist tables would use more than 1GB of memory, so skipping that check
  record:
  xapian-check: DatabaseCorruptError: Db block overwrit&lt;/pre&gt;</description>
    <dc:creator>Jed Brown</dc:creator>
    <dc:date>2013-05-09T21:58:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/14915">
    <title>attachment with missing Content-Disposition</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/14915</link>
    <description>&lt;pre&gt;Hi,

I recently received a multipart email with one of the parts being a pdf but the
part was not marked with "Content-Disposition: attachment". This let to notmuch
not adding tag:attachment to it.

The sender assured me that he used Outlook 2013 but I can't reproduce the
problem myself as I dont have microsoft products at hand. But if Outlook 2013
indeed adds attachments without setting "Content-Disposition: attachment", then
maybe the problem of notmuch not recognizing them as such is more severe?

The question is also what to do about it and how to detect attachments of this
kind. Apparently Thunderbird detects attachments that dont say
"Content-Disposition: attachment" but I did not try to figure out what its
heuristic is. Also the microsoft exchange server web client is able to figure
out that this part is supposed to be an attachment. What do other MUAs do?

So how to create a good heuristic? Using the Content-Type? In my case, the
supposed attachment was "application/octet-stream" for which it is prob&lt;/pre&gt;</description>
    <dc:creator>Johannes Schauer</dc:creator>
    <dc:date>2013-05-08T13:15:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/14910">
    <title>Solaris support - missing or incompatible functions</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/14910</link>
    <description>&lt;pre&gt;Hi,

This is next series of patches adding Solaris support to notmuch. I am mostly
using what Blake Jones sent some time ago + I fixed all the comments he
received back then. Since it's mostly his work, it's IMO fair to keep
him as an author. But since I made sure the patches work, I'm signing
them. I'm really git newbie, so hopefully this is right thing to do ...

I tested the build on Solaris using Oracle Studio and on Linux using
gcc (to make sure I haven't break anything).

I can't run the notmuch 'make test' on Solaris (too old bash) and on linux the
results are

421/525 tests passed.
25 tests failed.
79 tests skipped.

but they are the same without my changes too ...

Cheers
&lt;/pre&gt;</description>
    <dc:creator>Vladimir.Marek-QHcLZuEGTsvQT0dZR+AlfA&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2013-05-06T15:15:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.mail.notmuch.general/14908">
    <title>[CLI] bug in notmuch setup</title>
    <link>http://comments.gmane.org/gmane.mail.notmuch.general/14908</link>
    <description>&lt;pre&gt;Hi all,

As mentioned on IRC earlier, current master seems to have an issue with `notmuch setup`,
which fails to write ~/.notmuch-config if not already present.

Here are excerpts from the discussion from #notmuch:
--------------------------------------%&amp;lt;---------------------------------------
19:08:29 &amp;lt;pazz&amp;gt; i have no notmuch config so far. when i run `notmuch` i get questioned about my name and so forth. 
                then:
19:08:31 &amp;lt;pazz&amp;gt; Error canonicalizing /home/pazz/.notmuch-config: No such file or directory
19:14:01 &amp;lt;bremner&amp;gt; it could also be a bug. There was some change recently to avoid overwriting symlinks with files.
19:15:29 &amp;lt;bremner&amp;gt; pazz: I think you found a bug. try "touch .notmuch-config" and run notmuch-setup again.
19:21:54 &amp;lt;pazz&amp;gt; bremner: i'm a little confused because i thought i'd done that already. anyway: notmuch setup 
                fails iff there is no ~/.notmuch-config present.
19:22:38 &amp;lt;pazz&amp;gt; if there is an empty file notmuch setup runs ok, exit code is 0 and the file gets ov&lt;/pre&gt;</description>
    <dc:creator>Patrick Totzke</dc:creator>
    <dc:date>2013-05-05T21:22:44</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.mail.notmuch.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.mail.notmuch.general</link>
  </textinput>
</rdf:RDF>
