From: Lars Ingebrigtsen <larsi@gnus.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 56773@debbugs.gnu.org
Subject: bug#56773: 29.0.50; (readablep UNREADABLE) causes strange things
Date: Thu, 28 Jul 2022 12:46:30 +0200 [thread overview]
Message-ID: <87lesdwm49.fsf@gnus.org> (raw)
In-Reply-To: <8735elqzxa.fsf@yahoo.com> (Po Lu's message of "Thu, 28 Jul 2022 18:44:49 +0800")
Po Lu <luangruo@yahoo.com> writes:
> I don't think that's very intuitive, since signalling means "get me out
> of here now".
But we shouldn't leave things in an inconsistent state, and I suspect
that we currently do.
By the way, did you look at the test failure your change led to?
next prev parent reply other threads:[~2022-07-28 10:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 3:42 bug#56773: 29.0.50; (readablep UNREADABLE) causes strange things Michael Heerdegen
2022-07-26 12:31 ` Lars Ingebrigtsen
2022-07-26 12:39 ` Eli Zaretskii
2022-07-26 12:44 ` Lars Ingebrigtsen
2022-07-26 13:12 ` Eli Zaretskii
2022-07-26 13:24 ` Lars Ingebrigtsen
2022-07-27 9:30 ` Lars Ingebrigtsen
2022-07-27 9:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-27 9:51 ` Lars Ingebrigtsen
2022-07-27 9:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-27 9:58 ` Lars Ingebrigtsen
2022-07-27 11:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-28 1:47 ` Michael Heerdegen
2022-07-28 2:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-28 9:48 ` Lars Ingebrigtsen
2022-07-28 10:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-28 10:46 ` Lars Ingebrigtsen [this message]
2022-07-28 11:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-28 11:09 ` Lars Ingebrigtsen
2022-07-28 11:21 ` Po Lu 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lesdwm49.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=56773@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=michael_heerdegen@web.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 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.