unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrii Kolomoiets <andreyk.mad@gmail.com>
To: Alan Third <alan@idiocy.org>
Cc: Illia Ostapyshyn <ilya.ostapyshyn@gmail.com>, 48406@debbugs.gnu.org
Subject: bug#48406: 28.0.50; Emacs stuck in infinite loop in wait_reading_process_output when opening in fullscreen (NS)
Date: Sun, 16 May 2021 23:09:39 +0300	[thread overview]
Message-ID: <m2cztqfnjw.fsf@gmail.com> (raw)
In-Reply-To: <YKBPdtYQspvSFNz7@breton.holly.idiocy.org> (Alan Third's message of "Sat, 15 May 2021 23:47:18 +0100")

Alan Third <alan@idiocy.org> writes:

> You know, I'm probably being stupid, but I can't for the life of me
> remember why we need to wait for the fullscreen transition to
> complete. I *thought* it was because we had a crash if we didn't, but
> if I remove the wait it all works just fine...

Same here.  The code snippets provided in Bug#28496 and Bug#36672 are
works fine.

> It could be that it's pure chance I'm not seeing any problems, or that
> some other fix has fixed the crash,

Yes, the NS port certainly made a good progress, thank you :)

> or that the older drawing scheme used before 10.14 has a problem and
> the new one doesn't... Or something else. Do you have any idea?

This is the only example that comes to my mind for now:

(progn
  (toggle-frame-fullscreen)
  (toggle-frame-fullscreen))

Though code like this is not widely used (hope so), it's still some kind
of unexpected behavior.

> I *do* remember that there was a pause required for the non-native
> fullscreen due to a crash, and I don't think that will have changed,
> except that I don't think I've heard from anyone still using 10.6 for
> a couple of years now.

Well, we can pause for the non-native fullscreen users.


-- 
Andrii





  reply	other threads:[~2021-05-16 20:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-13 20:39 bug#48406: 28.0.50; Emacs stuck in infinite loop in wait_reading_process_output when opening in fullscreen (NS) Illia Ostapyshyn
2021-05-13 21:15 ` Alan Third
2021-05-14  6:07   ` Andrii Kolomoiets
2021-05-14  9:13     ` Illia Ostapyshyn
2021-05-14 19:32       ` Andrii Kolomoiets
2021-05-14 20:34         ` Alan Third
2021-05-15 19:44           ` Andrii Kolomoiets
2021-05-15 22:47             ` Alan Third
2021-05-16 20:09               ` Andrii Kolomoiets [this message]
2021-05-26 20:26                 ` Alan Third
2021-05-26 20:28                   ` Alan Third
2021-06-05 13:45                 ` Alan Third
2021-06-05 16:21                   ` Illia Ostapyshyn
2021-06-05 16:33                     ` Alan Third
2021-06-09 21:01                       ` Alan Third
2021-05-14 22:53         ` Filipp Gunbin
2021-05-15  8:34         ` Illia Ostapyshyn
2021-05-14  6:22 ` Eli Zaretskii
2021-05-14  9:22   ` Illia Ostapyshyn
2021-05-14 10:55     ` Eli Zaretskii
2021-05-14 11:09       ` Illia Ostapyshyn
2021-05-14 11:13         ` 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=m2cztqfnjw.fsf@gmail.com \
    --to=andreyk.mad@gmail.com \
    --cc=48406@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=ilya.ostapyshyn@gmail.com \
    /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).