unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Mattias Engdegård" <mattias.engdegard@gmail.com>
To: Basil Contovounesios <contovob@tcd.ie>
Cc: Eli Zaretskii <eliz@gnu.org>,
	64404@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#64404: 30.0.50; condition-case-unless-debug mishandles :success
Date: Sun, 2 Jul 2023 11:57:25 +0200	[thread overview]
Message-ID: <88ACE707-A181-4D76-9773-A1B772C28CC1@gmail.com> (raw)
In-Reply-To: <87sfa7bf7p.fsf@epfl.ch>

> 2. M-: (condition-case-unless-debug nil 1 (:success 2)) RET
>   => 1
> 
> This can easily be fixed in condition-case-unless-debug, and worked
> around by using explicit 'debug' with condition-case, but I was
> wondering if we want to do anything differently in
> internal_lisp_condition_case or the byte-compiler (e.g. new warning)
> instead?

Good catch! I don't think we need to bother about the Lisp interpreter, but I added a byte-compiler warning for it in 59a350cb91.
Would you like to repair condition-case-unless-debug?






  parent reply	other threads:[~2023-07-02  9:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-01 19:32 bug#64404: 30.0.50; condition-case-unless-debug mishandles :success Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-02  4:50 ` Eli Zaretskii
2023-07-02  9:57 ` Mattias Engdegård [this message]
2023-07-03  9:24   ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-03 10:09     ` Mattias Engdegård
2023-07-03 11:10       ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-03 11:12         ` Mattias Engdegård
2023-07-08 12:26           ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=88ACE707-A181-4D76-9773-A1B772C28CC1@gmail.com \
    --to=mattias.engdegard@gmail.com \
    --cc=64404@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --cc=eliz@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 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).