From: David Bremner <david@tethera.net>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: [PATCH 1/3] ruby: add new Database.open_with_config
Date: Mon, 28 Jun 2021 11:11:16 -0300 [thread overview]
Message-ID: <87h7hiaxkr.fsf@tethera.net> (raw)
In-Reply-To: <CAMP44s0FAb4_T2OLBEXRtnh4b3w=q3JvAEJHMMHD2n5O6xNwcw@mail.gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> writes:
> On Sun, Jun 27, 2021 at 1:02 PM David Bremner <david@tethera.net> wrote:
>>
>> Felipe Contreras <felipe.contreras@gmail.com> writes:
>>
>> > + ret = notmuch_database_open_with_config (database_path, mode,
>> > + config_path, profile, &db,
>> > + NULL);
>>
>> I'm curious why you ignore the error_message ouput parameter. Of course
>> it's valid and supported for library users to do this, but this way
>> there is no way for users of the ruby bindings to retrieve the
>> additional information about the error. Particularly in the case of
>> Xapian exceptions, this can be helpful for debugging.
>
> Because the patch is complex enough as it is. It shouldn't be that
> difficult to add a new notmuch_rb_status_raise function that takes an
> error message and produces a proper Ruby exception with that message,
> but that should be done in a separate patch.
>
Agreed.
d
next prev parent reply other threads:[~2021-06-28 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 3:28 [PATCH 0/3] ruby: add latest config API Felipe Contreras
2021-06-04 3:28 ` [PATCH 1/3] ruby: add new Database.open_with_config Felipe Contreras
2021-06-27 18:02 ` David Bremner
2021-06-27 18:17 ` Felipe Contreras
2021-06-28 14:11 ` David Bremner [this message]
2021-06-04 3:29 ` [PATCH 2/3] ruby: add db.config Felipe Contreras
2021-06-04 3:35 ` Felipe Contreras
2021-06-04 3:29 ` [PATCH 3/3] ruby: make db.config return an enumerator Felipe Contreras
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=87h7hiaxkr.fsf@tethera.net \
--to=david@tethera.net \
--cc=felipe.contreras@gmail.com \
--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).