unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: juri@linkov.net
Cc: 60096@debbugs.gnu.org
Subject: bug#60096: 29.0.60; Crash in format_mode_line_unwind_data
Date: Fri, 16 Dec 2022 16:39:57 +0200	[thread overview]
Message-ID: <83ilibjttu.fsf@gnu.org> (raw)
In-Reply-To: <83k02rk1vk.fsf@gnu.org> (message from Eli Zaretskii on Fri, 16 Dec 2022 13:46:07 +0200)

> Cc: 60096@debbugs.gnu.org
> Date: Fri, 16 Dec 2022 13:46:07 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > From: Juri Linkov <juri@linkov.net>
> > Cc: 60096-done@debbugs.gnu.org
> > Date: Fri, 16 Dec 2022 09:31:36 +0200
> > 
> > I confirm that it's fixed, so closing.
> > 
> > PS: I wonder why now *scratch* shows keybindings inside
> > non-standard quotation marks: "C-x C-f"?  Why not 'C-x C-f'?
> > Or `C-x C-f'?
> 
> I'm working on a better fix for this, which will revert back to how we
> were showing the bindings originally.  Whether what we did originally
> is the best way is a separate issue.

Now done, please re-test.

Note that the *scratch* buffer is re-created in this scenario without
the blurb we put into it, and in Fundamental mode.  This is because
get-scratch-buffer-create, which is called to re-create it (because we
have no "other" buffer to switch to when the original *scratch* is
killed) signals an error when it deletes the temp buffer used by
substitute-command-keys.  This is what happens when safe C code which
can be called in situations where we literally pull ourselves by the
shoestrings, is replaced by less safe Lisp code.





  reply	other threads:[~2022-12-16 14:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 17:04 bug#60096: 29.0.60; Crash in format_mode_line_unwind_data Juri Linkov
2022-12-15 21:42 ` Eli Zaretskii
2022-12-16  7:31   ` Juri Linkov
2022-12-16 11:46     ` Eli Zaretskii
2022-12-16 14:39       ` Eli Zaretskii [this message]
2022-12-16 15:03         ` Eli Zaretskii
2022-12-17  9:17           ` martin rudalics
2022-12-17 10:00             ` Eli Zaretskii
2022-12-17 10:53               ` Eli Zaretskii
2022-12-17 15:26               ` martin rudalics
2022-12-17 15:59                 ` Eli Zaretskii
2022-12-17 17:05                   ` martin rudalics
2022-12-17 17:52                     ` Eli Zaretskii
2022-12-18  9:18                       ` martin rudalics
2022-12-18 11:40                         ` Eli Zaretskii
2022-12-17 17:23           ` Juri Linkov
2022-12-17 17:59             ` Eli Zaretskii

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=83ilibjttu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60096@debbugs.gnu.org \
    --cc=juri@linkov.net \
    /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).