all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, 56773@debbugs.gnu.org
Subject: bug#56773: 29.0.50; (readablep UNREADABLE) causes strange things
Date: Tue, 26 Jul 2022 14:44:31 +0200	[thread overview]
Message-ID: <8735eo2gcw.fsf@gnus.org> (raw)
In-Reply-To: <83pmhscajq.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 26 Jul 2022 15:39:53 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> unwind_protect?

Where would the unwind_protect be?

The problem is here:

  if (!NILP (Vprint_unreadable_function)
      && FUNCTIONP (Vprint_unreadable_function))
    {
      specpdl_ref count = SPECPDL_INDEX ();
      /* Bind `print-unreadable-function' to nil to avoid accidental
	 infinite recursion in the function called.  */
      Lisp_Object func = Vprint_unreadable_function;
      specbind (Qprint_unreadable_function, Qnil);
      Lisp_Object result = CALLN (Ffuncall, func, obj,
				  escapeflag? Qt: Qnil);

We need to switch back to the original buffer before that Ffuncall, but
we don't know what the original function was -- it's just stored in a
local variable in prin1(-to-string).






  reply	other threads:[~2022-07-26 12:44 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 [this message]
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
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=8735eo2gcw.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=56773@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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.