Re: bug report

Valentin Kuznetsov writes: > Hi, > I'm new to notmuch system, but I used the tool for quite some time which is > integrated with my mutt setup. > > I found that the following query does not return any results > notmuch search CSBS-D-20-00016 > while if I do this query > notmuch search

Re: Bug report: crash of notmuch insert

On 12/12/2017, Tomi Ollila wrote: [snip] > > Have you ruled out an actual file size problem? This could be related to > > the environment notmuch insert is running in; I have a vague memory of a > > related issue encountered by a Postfix user. > > Adam, > > Does `ulimit -f` help ? what does it

Re: Bug report: crash of notmuch insert

On Tue, Dec 12 2017, David Bremner wrote: > "Adam C. Emerson" writes: > >> I am running notmuch 0.25.2 with Xapain version 1.4.4 on Arch >> Linux. The problem started with the default build, and to debug it I >> recompiled both packages with -O0 -g3. >> >> The backtrace looks

Re: Bug report: crash of notmuch insert

"Adam C. Emerson" writes: > I am running notmuch 0.25.2 with Xapain version 1.4.4 on Arch > Linux. The problem started with the default build, and to debug it I > recompiled both packages with -O0 -g3. > > The backtrace looks like: > > Using host libthread_db library

Bug report: crash of notmuch insert

Hello. For the last couple weeks I've been getting unpredictable crashes in notmuch insert. Once it starts happening, if I run notmuch compact it will stop happening for a while, then start up again later. I'm running it from procmail, in this case: * .* | reformail -f0 | notmuch insert +inbox

Re: bug report

Andy Wills writes: > Hi, > > I've been consistently getting an error of this form: > > andy@andy-x200:~/work/talks/2017/icps$ notmuch new > Processed 230 total files in 7s (29 files/sec.). > Added 212 new messages to the database. Removed 85 messages. Detected 18 file >

Re: bug report

Rafael Avila de Espindola writes: > David Bremner writes: > >> It's hard to be sure without more details, but it sounds like a locking >> problem, which could also be be fixed by upgrading to current xapian and >> notmuch. > > I currently have

Re: bug report

David Bremner writes: > It's hard to be sure without more details, but it sounds like a locking > problem, which could also be be fixed by upgrading to current xapian and > notmuch. I currently have notmuch-0.23.5-1.fc25.x86_64 and xapian-core-1.2.24-1.fc25.x86_64. I haven't

Re: bug report

Rafael Avila de Espindola writes: andy@andy-x200:~/work/talks/2017/icps$ notmuch new Processed 230 total files in 7s (29 files/sec.). Added 212 new messages to the database. Removed 85 messages. Detected 18 file renames. Error: A Xapian

Re: bug report

>>> andy@andy-x200:~/work/talks/2017/icps$ notmuch new >>> Processed 230 total files in 7s (29 files/sec.). >>> Added 212 new messages to the database. Removed 85 messages. Detected 18 >>> file renames. >>> Error: A Xapian exception occurred flushing database: Value in posting list >>> too

Re: bug report

David Bremner writes: > Andy Wills writes: > >> >> andy@andy-x200:~/work/talks/2017/icps$ notmuch new >> Processed 230 total files in 7s (29 files/sec.). >> Added 212 new messages to the database. Removed 85 messages. Detected 18 >> file renames. >>

Re: bug report

Andy Wills writes: > > andy@andy-x200:~/work/talks/2017/icps$ notmuch new > Processed 230 total files in 7s (29 files/sec.). > Added 212 new messages to the database. Removed 85 messages. Detected 18 file > renames. > Error: A Xapian exception occurred flushing database:

bug report

Hi, I've been consistently getting an error of this form: andy@andy-x200:~/work/talks/2017/icps$ notmuch new Processed 230 total files in 7s (29 files/sec.). Added 212 new messages to the database. Removed 85 messages. Detected 18 file renames. Error: A Xapian exception occurred flushing

RE: notmuch-0.21 bug report

Hello there, > Hi David; > > Thanks for the report. fclose doesn't really make sense here; Surprising. There is a call to fclose for the success return, so I just assumed that one would also be required for the error return. >what is that error message

RE: notmuch-0.21 bug report

David Binderman writes: > Hello there, > > >> Hi David; >> >> Thanks for the report. fclose doesn't really make sense here; > > Surprising. There is a call to fclose for the success return, > so I just assumed that one would also be

Re: notmuch-0.21 bug report

David Binderman writes: > Hello there, > > [notmuch-count.c:207]: (error) Resource leak: input > > Source code is > >    if (notmuch_database_open (notmuch_config_get_database_path (config), >    NOTMUCH_DATABASE_MODE_READ_ONLY, )) >     return EXIT_FAILURE;

notmuch-0.21 bug report

Hello there, [notmuch-count.c:207]: (error) Resource leak: input Source code is    if (notmuch_database_open (notmuch_config_get_database_path (config),    NOTMUCH_DATABASE_MODE_READ_ONLY, ))     return EXIT_FAILURE; Suggest call fclose. Some duplicates:

Re: Bug report: undeletable traces of ghosts in the notmuch database

On Thu 2016-01-14 16:20:59 -0500, Daniel Kahn Gillmor wrote: > This suggests that if i include a bogus message-id in my References: > list for any mail i send to a notmuch user, then access to their > database will let me tell whether they ever saw it or not, regardless of > whether they deleted

Bug report: undeletable traces of ghosts in the notmuch database

If i add a message to my notmuch database that includes References: or In-Reply-To: of a message-id that i don't have, notmuch creates a "ghost" entry in the database. If i remove the message from my mail archive, and then re-run "notmuch new", i'd expect all traces of that message to be gone

bug report: Emacs notmuch-mode fails attachments with spaces

David Edmondson writes: > On Tue, Feb 10 2015, Nils Dagsson Moskopp wrote: >> Tomi Ollila writes: >> >>> On Mon, Feb 09 2015, Nils Dagsson Moskopp >> dieweltistgarnichtso.net> wrote: >>> Dear notmuch developers, I use notmuch-mode for GNU Emacs for managing my email.

Re: bug report: Emacs notmuch-mode fails attachments with spaces

David Edmondson d...@dme.org writes: On Tue, Feb 10 2015, Nils Dagsson Moskopp wrote: Tomi Ollila tomi.oll...@iki.fi writes: On Mon, Feb 09 2015, Nils Dagsson Moskopp n...@dieweltistgarnichtso.net wrote: Dear notmuch developers, I use notmuch-mode for GNU Emacs for managing my email.

bug report: Emacs notmuch-mode fails attachments with spaces

Tomi Ollila writes: > > ... but we could let-bind shell-file-name... > If that seems needed, I think I'd rather push the bug upstream.

Re: bug report: Emacs notmuch-mode fails attachments with spaces

Tomi Ollila tomi.oll...@iki.fi writes: ... but we could let-bind shell-file-name... If that seems needed, I think I'd rather push the bug upstream. ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch

bug report: Emacs notmuch-mode fails attachments with spaces

On Wed, Feb 11 2015, Tomi Ollila wrote: > On Tue, Feb 10 2015, Nils Dagsson Moskopp > wrote: > >> Tomi Ollila writes: >> It seems to me that all of the following are true in this case: >> >> 1. Emacs executes the user's default shell to start zathura. > > That's stupid! it should run

Re: bug report: Emacs notmuch-mode fails attachments with spaces

On Wed, Feb 11 2015, Tomi Ollila tomi.oll...@iki.fi wrote: On Tue, Feb 10 2015, Nils Dagsson Moskopp n...@dieweltistgarnichtso.net wrote: Tomi Ollila tomi.oll...@iki.fi writes: It seems to me that all of the following are true in this case: 1. Emacs executes the user's default shell to

bug report: Emacs notmuch-mode fails attachments with spaces

On Tue, Feb 10 2015, Nils Dagsson Moskopp wrote: > Tomi Ollila writes: > >> On Mon, Feb 09 2015, Nils Dagsson Moskopp >> wrote: >> >>> Dear notmuch developers, >>> >>> >>> I use notmuch-mode for GNU Emacs for managing my email. >>> >>> I think I have found a bug in notmuch-mode: If I do

Re: bug report: Emacs notmuch-mode fails attachments with spaces

On Tue, Feb 10 2015, Nils Dagsson Moskopp n...@dieweltistgarnichtso.net wrote: Tomi Ollila tomi.oll...@iki.fi writes: On Mon, Feb 09 2015, Nils Dagsson Moskopp n...@dieweltistgarnichtso.net wrote: Dear notmuch developers, I use notmuch-mode for GNU Emacs for managing my email. I think

bug report: Emacs notmuch-mode fails attachments with spaces

David Bremner writes: > Tomi Ollila writes: > >> SO, there is 2 options: >> >> 1) mm executes save part correctly but not display part >> >> 2) there is (shell) wrapper program executing zathura which cannot handle >>arguments with spaces (there is plenty of examples of this!) >> > > For

bug report: Emacs notmuch-mode fails attachments with spaces

Tomi Ollila writes: > On Mon, Feb 09 2015, Nils Dagsson Moskopp > wrote: > >> Dear notmuch developers, >> >> >> I use notmuch-mode for GNU Emacs for managing my email. >> >> I think I have found a bug in notmuch-mode: If I do ?.-v? on the line ?[ >> 2015 _ Richtlinien.pdf: application/pdf ]?,

bug report: Emacs notmuch-mode fails attachments with spaces

On Tue, Feb 10 2015, Nils Dagsson Moskopp wrote: > Tomi Ollila writes: > >> On Mon, Feb 09 2015, Nils Dagsson Moskopp >> wrote: >> >>> Dear notmuch developers, >>> >>> >>> I use notmuch-mode for GNU Emacs for managing my email. >>> >>> I think I have found a bug in notmuch-mode: If I do ?.-v?

bug report: Emacs notmuch-mode fails attachments with spaces

On Mon, Feb 09 2015, Nils Dagsson Moskopp wrote: > Dear notmuch developers, > > > I use notmuch-mode for GNU Emacs for managing my email. > > I think I have found a bug in notmuch-mode: If I do ?.-v? on the line ?[ > 2015 _ Richtlinien.pdf: application/pdf ]?, then notmuch will open three >

bug report: Emacs notmuch-mode fails attachments with spaces

Tomi Ollila writes: > SO, there is 2 options: > > 1) mm executes save part correctly but not display part > > 2) there is (shell) wrapper program executing zathura which cannot handle >arguments with spaces (there is plenty of examples of this!) > For what it's worth, emacs-24.4 /

Re: bug report: Emacs notmuch-mode fails attachments with spaces

David Bremner da...@tethera.net writes: Tomi Ollila tomi.oll...@iki.fi writes: SO, there is 2 options: 1) mm executes save part correctly but not display part 2) there is (shell) wrapper program executing zathura which cannot handle arguments with spaces (there is plenty of examples of

Re: bug report: Emacs notmuch-mode fails attachments with spaces

Tomi Ollila tomi.oll...@iki.fi writes: On Mon, Feb 09 2015, Nils Dagsson Moskopp n...@dieweltistgarnichtso.net wrote: Dear notmuch developers, I use notmuch-mode for GNU Emacs for managing my email. I think I have found a bug in notmuch-mode: If I do “.-v” on the line “[ 2015 _

Re: bug report: Emacs notmuch-mode fails attachments with spaces

On Tue, Feb 10 2015, Nils Dagsson Moskopp wrote: Tomi Ollila tomi.oll...@iki.fi writes: On Mon, Feb 09 2015, Nils Dagsson Moskopp n...@dieweltistgarnichtso.net wrote: Dear notmuch developers, I use notmuch-mode for GNU Emacs for managing my email. I think I have found a bug in

Re: bug report: Emacs notmuch-mode fails attachments with spaces

Tomi Ollila tomi.oll...@iki.fi writes: SO, there is 2 options: 1) mm executes save part correctly but not display part 2) there is (shell) wrapper program executing zathura which cannot handle arguments with spaces (there is plenty of examples of this!) For what it's worth, emacs-24.4

bug report: Emacs notmuch-mode fails attachments with spaces

Dear notmuch developers, I use notmuch-mode for GNU Emacs for managing my email. I think I have found a bug in notmuch-mode: If I do ?.-v? on the line ?[ 2015 _ Richtlinien.pdf: application/pdf ]?, then notmuch will open three windows of zathura (the PDF viewer I use). It seems to me that

bug report: Emacs notmuch-mode fails attachments with spaces

Dear notmuch developers, I use notmuch-mode for GNU Emacs for managing my email. I think I have found a bug in notmuch-mode: If I do “.-v” on the line “[ 2015 _ Richtlinien.pdf: application/pdf ]”, then notmuch will open three windows of zathura (the PDF viewer I use). It seems to me that

Re: bug report: Emacs notmuch-mode fails attachments with spaces

On Mon, Feb 09 2015, Nils Dagsson Moskopp n...@dieweltistgarnichtso.net wrote: Dear notmuch developers, I use notmuch-mode for GNU Emacs for managing my email. I think I have found a bug in notmuch-mode: If I do “.-v” on the line “[ 2015 _ Richtlinien.pdf: application/pdf ]”, then notmuch

notmuch-emacs bug report -- infinite looping trying to select next message

the problem I end up with this in the buffer: [ message/external-body ] !!! Bodypart insert error: Couldn't find access type !!! [ text/plain ] so I think it's pretty likely your guess is accurate. > Thanks so much for including a test case with your bug report, No problem, thank

Re: notmuch-emacs bug report -- infinite looping trying to select next message

with this in the buffer: [ message/external-body ] !!! Bodypart insert error: Couldn't find access type !!! [ text/plain ] so I think it's pretty likely your guess is accurate. Thanks so much for including a test case with your bug report, No problem, thanks for checking

notmuch-emacs bug report -- infinite looping trying to select next message

ng to assume something fixed it in the intervening years. In particular our handling of error reporting for corrupted parts changed, so maybe that was it. Thanks so much for including a test case with your bug report, d

Re: notmuch-emacs bug report -- infinite looping trying to select next message

I'm going to assume something fixed it in the intervening years. In particular our handling of error reporting for corrupted parts changed, so maybe that was it. Thanks so much for including a test case with your bug report, d ___ notmuch mailing list

notmuch-emacs bug report -- infinite looping trying to select next message

Hi Michael, On Wed, 15 Feb 2012 10:57:42 +1300, Michael Hudson-Doyle wrote: > Thanks for the reply! > > On Tue, 14 Feb 2012 10:41:20 +0100, Rodney Lorrimar > wrote: > > Hi Michael, > > > > On Tue, 14 Feb 2012 11:01:56 +1300, Michael Hudson-Doyle > canonical.com> wrote: > > > The attached

Re: notmuch-emacs bug report -- infinite looping trying to select next message

Hi Michael, On Wed, 15 Feb 2012 10:57:42 +1300, Michael Hudson-Doyle michael.hud...@canonical.com wrote: Thanks for the reply! On Tue, 14 Feb 2012 10:41:20 +0100, Rodney Lorrimar d...@rodney.id.au wrote: Hi Michael, On Tue, 14 Feb 2012 11:01:56 +1300, Michael Hudson-Doyle

notmuch-emacs bug report -- infinite looping trying to select next message

Thanks for the reply! On Tue, 14 Feb 2012 10:41:20 +0100, Rodney Lorrimar wrote: > Hi Michael, > > On Tue, 14 Feb 2012 11:01:56 +1300, Michael Hudson-Doyle canonical.com> wrote: > > The attached gzipped mbox appears to trip up the emacs interface. The > > problem seems to come from the

notmuch-emacs bug report -- infinite looping trying to select next message

The attached gzipped mbox appears to trip up the emacs interface. The problem seems to come from the message with id CAGNsrLCWv6=36q+q+5Hc_SzgdZ2ergeKkapT7T3xXvim=2cK+A at mail.gmail.com. If you load up the thread in emacs, you get a message: mm-extern-cache-contents: Couldn't find access type

notmuch-emacs bug report -- infinite looping trying to select next message

Hi Michael, On Tue, 14 Feb 2012 11:01:56 +1300, Michael Hudson-Doyle wrote: > The attached gzipped mbox appears to trip up the emacs interface. The > problem seems to come from the message with id > CAGNsrLCWv6=36q+q+5Hc_SzgdZ2ergeKkapT7T3xXvim=2cK+A at mail.gmail.com. > > If you load up the

Re: notmuch-emacs bug report -- infinite looping trying to select next message

Hi Michael, On Tue, 14 Feb 2012 11:01:56 +1300, Michael Hudson-Doyle michael.hud...@canonical.com wrote: The attached gzipped mbox appears to trip up the emacs interface. The problem seems to come from the message with id CAGNsrLCWv6=36q+q+5Hc_SzgdZ2ergeKkapT7T3xXvim=2c...@mail.gmail.com.

Re: notmuch-emacs bug report -- infinite looping trying to select next message

Thanks for the reply! On Tue, 14 Feb 2012 10:41:20 +0100, Rodney Lorrimar d...@rodney.id.au wrote: Hi Michael, On Tue, 14 Feb 2012 11:01:56 +1300, Michael Hudson-Doyle michael.hud...@canonical.com wrote: The attached gzipped mbox appears to trip up the emacs interface. The problem

notmuch-emacs bug report -- infinite looping trying to select next message

The attached gzipped mbox appears to trip up the emacs interface. The problem seems to come from the message with id CAGNsrLCWv6=36q+q+5Hc_SzgdZ2ergeKkapT7T3xXvim=2c...@mail.gmail.com. If you load up the thread in emacs, you get a message: mm-extern-cache-contents: Couldn't find access type

bug report: notmuch-hello 'All tags' view

On Wed, 03 Nov 2010, Jameson Rollins wrote: > On Wed, 03 Nov 2010 22:57:55 +0100, Michal Sojka > wrote: > > I can confirm this with 0.4 debian package. notmuch search-tags outputs > > first line as empty and emacs shows it in All tags view. > > Again, this is *not* what I am seeing. Michael,

bug report: notmuch-hello 'All tags' view

On Tue, 02 Nov 2010 20:17:56 +, Darren McGuicken wrote: > Wow, that was probably the most secure bug report in history - this time > in plain for those of you who don't have access to Carl's private key! > > I've noticed since rebasing to 0.4 that I'm seeing an empty entry in the

bug report: notmuch-hello 'All tags' view

On Tue, 02 Nov 2010 17:33:08 -0400, Jameson Rollins wrote: > On Tue, 02 Nov 2010 21:03:55 +, Darren McGuicken fernseed.info> wrote: > > A call to 'notmuch search-tags' from the command line does indeed > > return an empty string as the first entry for me[1]. > > fwiw, I don't personally get

bug report: notmuch-hello 'All tags' view

On Wed, 03 Nov 2010 22:57:55 +0100, Michal Sojka wrote: > I can confirm this with 0.4 debian package. notmuch search-tags outputs > first line as empty and emacs shows it in All tags view. Again, this is *not* what I am seeing. Michael, are you sure you don't also have messages tagged with the

Re: bug report: notmuch-hello 'All tags' view

On Tue, 02 Nov 2010 17:33:08 -0400, Jameson Rollins jroll...@finestructure.net wrote: On Tue, 02 Nov 2010 21:03:55 +, Darren McGuicken mailing-notm...@fernseed.info wrote: A call to 'notmuch search-tags' from the command line does indeed return an empty string as the first entry for

Re: bug report: notmuch-hello 'All tags' view

On Tue, 02 Nov 2010 20:17:56 +, Darren McGuicken mailing-notm...@fernseed.info wrote: Wow, that was probably the most secure bug report in history - this time in plain for those of you who don't have access to Carl's private key! I've noticed since rebasing to 0.4 that I'm seeing

Re: bug report: notmuch-hello 'All tags' view

On Wed, 03 Nov 2010 22:57:55 +0100, Michal Sojka sojk...@fel.cvut.cz wrote: I can confirm this with 0.4 debian package. notmuch search-tags outputs first line as empty and emacs shows it in All tags view. Again, this is *not* what I am seeing. Michael, are you sure you don't also have messages

bug report: notmuch-hello 'All tags' view

On Tue, 02 Nov 2010 20:17:56 +, Darren McGuicken wrote: > I've noticed since rebasing to 0.4 that I'm seeing an empty entry in the > 'All tags' view of notmuch-hello which appears to represent a search > against 'tag:'. Continuing what's turning into an epic one-man list-noise generation

bug report: notmuch-hello 'All tags' view

Wow, that was probably the most secure bug report in history - this time in plain for those of you who don't have access to Carl's private key! I've noticed since rebasing to 0.4 that I'm seeing an empty entry in the 'All tags' view of notmuch-hello which appears to represent a search against

***UNCHECKED*** bug report: notmuch-hello 'All tags' view

A non-text attachment was scrubbed... Name: not available Type: application/pgp-encrypted Size: 11 bytes Desc: not available URL: -- next part -- A non-text attachment was scrubbed...

bug report: notmuch-hello 'All tags' view

On Tue, 02 Nov 2010 21:03:55 +, Darren McGuicken wrote: > A call to 'notmuch search-tags' from the command line does indeed return > an empty string as the first entry for me[1]. > > Does that point to bad data on my part, or has the output of > 'search-tags' changed recently? fwiw, I don't

Re: bug report: notmuch-hello 'All tags' view

Wow, that was probably the most secure bug report in history - this time in plain for those of you who don't have access to Carl's private key! I've noticed since rebasing to 0.4 that I'm seeing an empty entry in the 'All tags' view of notmuch-hello which appears to represent a search against

Re: bug report: notmuch-hello 'All tags' view

On Tue, 02 Nov 2010 20:17:56 +, Darren McGuicken mailing-notm...@fernseed.info wrote: I've noticed since rebasing to 0.4 that I'm seeing an empty entry in the 'All tags' view of notmuch-hello which appears to represent a search against 'tag:'. Continuing what's turning into an epic

Re: bug report: notmuch-hello 'All tags' view

On Tue, 02 Nov 2010 21:03:55 +, Darren McGuicken mailing-notm...@fernseed.info wrote: A call to 'notmuch search-tags' from the command line does indeed return an empty string as the first entry for me[1]. Does that point to bad data on my part, or has the output of 'search-tags' changed

bug report: xapian error for message id with '..'

On Wed, 28 Apr 2010 18:41:18 -0400, Jameson Rollins wrote: > So I think this means that the problem probably lies mostly in the emacs > UI not properly quoting the id string. What originally got me on this > problem is that I was not able to manipulate the tag of this email from > within emacs.

Re: bug report: xapian error for message id with '..'

On Wed, 28 Apr 2010 18:41:18 -0400, Jameson Rollins jroll...@finestructure.net wrote: So I think this means that the problem probably lies mostly in the emacs UI not properly quoting the id string. What originally got me on this problem is that I was not able to manipulate the tag of this

Re: bug report: xapian error for message id with '..'

On Fri, 22 Oct 2010 17:48:29 -0700, Carl Worth cwo...@cworth.org wrote: On Wed, 28 Apr 2010 18:41:18 -0400, Jameson Rollins jroll...@finestructure.net wrote: I also note here that notmuch is not returning an error, even though a Xapian exception occurred and the search failed. This is

bug report: xapian error for message id with '..'

I have a followup on this report. Olly suggested quoting the quoting of the id, so that the quoting gets properly passed to Xapian, and that seems to work: 0 servo:~ $ notmuch search id:'"4bd73e8cb3d79_1a3c..fb637ff610e at skinner.tmail"' thread:c4cf Yest. 15:44 [1/1]

bug report: xapian error for message id with '..'

I have received a message with a somewhat strange message Id that is causing problems in notmuch: Message-Id: <4bd73e8cb3d79_1a3c..fb637ff610e at skinner.tmail> Notmuch (or actually Xapian) seems to be interpreting the '..' as a range operator, which it doesn't know how to handle: 0 servo$

Re: bug report: xapian error for message id with '..'

I have a followup on this report. Olly suggested quoting the quoting of the id, so that the quoting gets properly passed to Xapian, and that seems to work: 0 servo:~ $ notmuch search id:'4bd73e8cb3d79_1a3c..fb637ff6...@skinner.tmail' thread:c4cf Yest. 15:44 [1/1]