From: Eli Zaretskii <eliz@gnu.org>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: luangruo@yahoo.com, 65193@debbugs.gnu.org
Subject: bug#65193: 29.1.50; SET_FRAME_ICONIFIED can cause Lisp evaluation inside read_socket_hook.
Date: Sat, 12 Aug 2023 10:30:40 +0300 [thread overview]
Message-ID: <83r0o8emzj.fsf@gnu.org> (raw)
In-Reply-To: <wlsf8qzdb9.wl-mituharu@math.s.chiba-u.ac.jp> (message from YAMAMOTO Mitsuharu on Fri, 11 Aug 2023 08:29:30 +0900)
> Date: Fri, 11 Aug 2023 08:29:30 +0900
> From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
> Cc: luangruo@yahoo.com,
> 65193@debbugs.gnu.org
>
> On Fri, 11 Aug 2023 02:58:50 +0900,
> Eli Zaretskii wrote:
> >
> > > Cc: 65193@debbugs.gnu.org
> > > Date: Fri, 11 Aug 2023 01:33:41 +0900
> > > From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
> > >
> > > Another problem specific to the NS port w.r.t. the call to
> > > gui_consider_frame_title from SET_FRAME_ICONIFIED is that it can
> > > also be called inside the select emulation via -[EmacsView
> > > windowDidDeminiaturize:] for example.
> >
> > Please describe in more detail how such a call could happen, including
> > the sequence of calls which could call SET_FRAME_ICONIFIED from the
> > select emulation. This situation, if it can happen, should be
> > investigated.
>
> Sorry, I thought the NS port can run another Lisp thread while one
> thread is waiting for inputs with (emulated) select as in other
> platforms (including the Mac port). But actually that's not the case,
> so the situation I said does not happen with the current NS select
> emulation. Of course, once the NS port obtains such ability, the
> problem I described will happen.
>
> Below is the stacktrace that leads to SET_FRAME_ICONIFIED from the NS
> select emulation (ns_select):
OK, thanks.
prev parent reply other threads:[~2023-08-12 7:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 7:41 bug#65193: 29.1.50; SET_FRAME_ICONIFIED can cause Lisp evaluation inside read_socket_hook YAMAMOTO Mitsuharu
2023-08-10 8:26 ` 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 [this message]
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=83r0o8emzj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65193@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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).