unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Illia Ostapyshyn <ilya.ostapyshyn@gmail.com>
Cc: 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: Fri, 14 May 2021 14:13:45 +0300	[thread overview]
Message-ID: <83zgwxy3di.fsf@gnu.org> (raw)
In-Reply-To: <8509173B-1C7E-4113-967C-DB635D1B6398@gmail.com> (message from Illia Ostapyshyn on Fri, 14 May 2021 13:09:47 +0200)

> From: Illia Ostapyshyn <ilya.ostapyshyn@gmail.com>
> Date: Fri, 14 May 2021 13:09:47 +0200
> Cc: 48406@debbugs.gnu.org
> 
> > On May 14, 2021, at 12:55, Eli Zaretskii <eliz@gnu.org> wrote:
> > 
> >> Like I mentioned, with this line in init.el Emacs exhibits the same behavior.
> >> 
> >> emacs -Q --execute "(push '(fullscreen . fullboth) default-frame-alist)"
> >> doesn't work as well.
> > 
> > "Doesn't work" in what sense?  What did you expect to happen and what
> > did indeed happen?
> > 
> > And the above line is definitely not for init.el, it's a command for
> > invoking Emacs from the shell prompt.  So I'm not sure I understand
> > what exactly did you try with that command.
> 
> Did not work in the sense of resolving the original issue of this bug
> report:
> 
> Invoking (push '(fullscreen . fullboth) default-frame-alist) during
> Emacs startup causes it to hang, no matter where it is, early-init.el,
> init.el or passed through --execute. Same goes for
> (toggle-frame-fullscreen) and everything else that makes Emacs switch
> to fullscreen mode.

If this fails in init.el, then we should fix that.  But I don't
promise the fix will make it work in early-init.el.





      reply	other threads:[~2021-05-14 11:13 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
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 [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=83zgwxy3di.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=48406@debbugs.gnu.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).