Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
From: Justus Winter <4winter@informatik.uni-hamburg.de>
User-Agent: alot/0.21+
To: David Bremner <david@tethera.net>,
	notmuch mailing list <notmuch@notmuchmail.org>
References: <20120221002921.8534.57091@thinkbox.jade-hamburg.de>
	<20120221155312.GB30513@mit.edu>
	<20120222151745.4213.93513@thinkbox.jade-hamburg.de>
	<20120223222200.17796.11840@thinkbox.jade-hamburg.de>
	<87hayhkr9r.fsf@zancas.localnet>
In-Reply-To: <87hayhkr9r.fsf@zancas.localnet>
Message-ID: <20120224010452.17796.73012@thinkbox.jade-hamburg.de>
Subject: Re: notmuch as a shared object aka library knigge
Date: Fri, 24 Feb 2012 02:04:52 +0100
Precedence: list

Quoting David Bremner (2012-02-24 01:29:36)
>On Thu, 23 Feb 2012 23:22:00 +0100, Justus Winter <4winter@informatik.uni-=
hamburg.de> wrote:
>
>> That wasn't meant to sound as harsh as it probably did. I seriously
>> hope that someone is around who enjoys to hack on the c/c++ part of
>> the library and is willing fix problems in it.
>
>Luckily I deleted my snarky reply ;).

*phew* ;)

>> And I worked around the two functions (that I know of) that call
>> exit(3) by conditionally raising exceptions in the python bindings,
>> but this is only meant as a intermediate fix, a hack that should be
>> removed as soon as the library is fixed.
>
>Can you make test cases to document exactly when internal errors are
>occuring in the library? Somehow it seems like the CLI is not triggering
>them. It might help clarify the discussion and/or motivate people to fix
>them.

I did ;) I provided a python program in my original mail for
Database.get_directory aka notmuch_database_get_directory and the one
for Database.find_message_by_filename aka
notmuch_database_find_message_by_filename can be trivially derived
from it (though you need a path to a mail within your maildir). It
should be straight forward to port those to c if you want to.

Justus