From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: 65193@debbugs.gnu.org
Subject: bug#65193: 29.1.50; SET_FRAME_ICONIFIED can cause Lisp evaluation inside read_socket_hook.
Date: Thu, 10 Aug 2023 16:41:16 +0900 [thread overview]
Message-ID: <wl7cq3mjj7.wl-mituharu@math.s.chiba-u.ac.jp> (raw)
SET_FRAME_ICONIFIED has a call to gui_consider_frame_title and it can
cause Lisp evaluation if icon-title-format or frame-title-format
contains (:eval FORM). This is problematic because
SET_FRAME_ICONIFIED can be called inside read_socket_hook.
The call to gui_consider_frame_title was introduced by the following
change:
commit e99f41f03a97641ee05ba4a27f8b91c190f55df1
Author: Po Lu <luangruo@yahoo.com>
Date: Thu Jun 9 21:48:19 2022 +0800
Fix recalculation of `icon-title-format' after a frame is iconified
Previously it would only happen upon the next mode line
redisplay, meaning that just pressing C-z would not update the
implicit title, since C-z doesn't cause a redisplay.
* src/dispextern.h: Update prototypes.
* src/frame.h (SET_FRAME_ICONIFIED): De-slugify. Call
`gui_consider_frame_title', since `icon-title-format' might be
different from the current frame title.
* src/xdisp.c (gui_consider_frame_title): Export (also in
dispextern.h). (bug#55850)
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next reply other threads:[~2023-08-10 7:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 7:41 YAMAMOTO Mitsuharu [this message]
2023-08-10 8:26 ` bug#65193: 29.1.50; SET_FRAME_ICONIFIED can cause Lisp evaluation inside read_socket_hook Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-10 9:21 ` YAMAMOTO Mitsuharu
2023-08-10 13:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-10 16:32 ` YAMAMOTO Mitsuharu
2023-08-11 0:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-10 16:33 ` YAMAMOTO Mitsuharu
2023-08-10 17:58 ` Eli Zaretskii
2023-08-10 23:29 ` YAMAMOTO Mitsuharu
2023-08-12 7:30 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wl7cq3mjj7.wl-mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=65193@debbugs.gnu.org \
/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.