From: Jonas Bernoulli <jonas@bernoul.li>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 58363@debbugs.gnu.org
Subject: bug#58363: [PATCH 2/3] Introduce a new sqlite-error
Date: Sat, 22 Oct 2022 12:47:10 +0200 [thread overview]
Message-ID: <871qr0rv81.fsf@bernoul.li> (raw)
In-Reply-To: <8735bg8bjy.fsf@gmx.de>
Michael Albinus <michael.albinus@gmx.de> writes:
> Jonas Bernoulli <jonas@bernoul.li> writes:
>
> Hi Jonas,
>
>> + DEFSYM (Qsqlite_error, "sqlite-error");
>> + Fput (Qsqlite_error, Qerror_conditions,
>> + Fpurecopy (list2 (Qsqlite_error, Qerror)));
>> + Fput (Qsqlite_error, Qerror_message,
>> + build_pure_c_string ("Database error"));
>> +
>> DEFSYM (Qsqlite_locked_error, "sqlite-locked-error");
>> Fput (Qsqlite_locked_error, Qerror_conditions,
>> - Fpurecopy (list2 (Qsqlite_locked_error, Qerror)));
>> + Fpurecopy (list3 (Qsqlite_locked_error, Qsqlite_error, Qerror)));
>> Fput (Qsqlite_locked_error, Qerror_message,
>> build_pure_c_string ("Database locked"));
>
> I'm not sure about our policy, but shouldn't error symbols in the C core
> be documented in the manual, node "(elisp) Standard Errors"?
>
> Best regards, Michael.
I don't know but that section begins with
> Here is a list of the more important error symbols in standard Emacs,
Maybe this new error symbol falls into that category.
sqlite-locked-error wasn't documented on that page,
so I didn't do it for this either, for now.
next prev parent reply other threads:[~2022-10-22 10:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 18:52 bug#58363: 29.0.50; sqlite-select does not signal errors and errors should be improved Jonas Bernoulli
2022-10-08 13:41 ` Lars Ingebrigtsen
2022-10-08 14:35 ` Eli Zaretskii
2022-10-08 14:51 ` Lars Ingebrigtsen
2022-10-08 22:47 ` Jonas Bernoulli
2022-10-09 14:18 ` Lars Ingebrigtsen
2022-10-10 10:56 ` Jonas Bernoulli
2022-10-11 0:23 ` Lars Ingebrigtsen
2022-10-14 17:52 ` Jonas Bernoulli
2022-10-21 21:06 ` bug#58363: [PATCH 0/3] Improve error data signaled by sqlite-execute et al Jonas Bernoulli
2022-10-21 21:06 ` bug#58363: [PATCH 1/3] Use xsignal1 as required by argument type Jonas Bernoulli
2022-10-22 6:45 ` Eli Zaretskii
2022-10-22 10:45 ` Jonas Bernoulli
2022-10-22 11:45 ` Eli Zaretskii
2022-10-22 15:32 ` Jonas Bernoulli
2022-10-22 15:59 ` Eli Zaretskii
2022-10-21 21:06 ` bug#58363: [PATCH 2/3] Introduce a new sqlite-error Jonas Bernoulli
2022-10-22 9:14 ` Michael Albinus
2022-10-22 10:47 ` Jonas Bernoulli [this message]
2022-10-21 21:06 ` bug#58363: [PATCH 3/3] Improve error data signaled by sqlite-execute et al Jonas Bernoulli
2022-10-22 6:49 ` Eli Zaretskii
2022-10-22 11:07 ` Jonas Bernoulli
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qr0rv81.fsf@bernoul.li \
--to=jonas@bernoul.li \
--cc=58363@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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://git.savannah.gnu.org/cgit/emacs.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).