From: Stefan Kangas <stefankangas@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, 72212@debbugs.gnu.org
Subject: bug#72212: 31.0.50; API for condition objects
Date: Sat, 14 Sep 2024 17:09:09 -0700 [thread overview]
Message-ID: <CADwFkmnPHMU=f3pq78f8Of=60y08Oinc9prxyrPUQ4FrTw4kVQ@mail.gmail.com> (raw)
In-Reply-To: <jwvfrr0u0g1.fsf-monnier+emacs@gnu.org>
Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:
> Wow, I did not expect such wild reactions!
;-)
FWIW, your patch looks good to me, and seems like it's moving in a good
direction.
>> Beside whether we want to do this or not, there is another question
>> about naming: currently we use "condition" in some places (e.g. in
>> `condition-case`) but we use "error" in others (e.g. `define-error` and
>> `error-message-string`). I chose to use "condition" in the patch below,
>> but I don't have a strong opinion on that choice, so I could go with
>> "error" if that's what other prefer. If we keep "condition" there's the
>> subsidiary question whether we should add aliases for `define-error` and
>> `error-message-string`.
I think we should keep the word "condition", and think we could have
aliases "define-condition" and "condition-message-string" like you
propose.
next prev parent reply other threads:[~2024-09-15 0:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-20 15:47 bug#72212: 31.0.50; API for condition objects Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-19 13:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-15 0:09 ` Stefan Kangas [this message]
2024-09-17 19:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-02 19:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-02 19:49 ` Eli Zaretskii
2024-11-02 22:37 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmnPHMU=f3pq78f8Of=60y08Oinc9prxyrPUQ4FrTw4kVQ@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=72212@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.