unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Sébastien Chapuis" <sebastien@chapu.is>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 37986@debbugs.gnu.org
Subject: bug#37986: emacsclient doesn't open a frame when waiting for input in the minibuffer
Date: Fri, 1 Nov 2019 21:35:24 +0800	[thread overview]
Message-ID: <CAN2Hsvx7Pmf1BaGSE36zcO21BpZgX28mvTGWwK3m2iOOqW2Ujg@mail.gmail.com> (raw)
In-Reply-To: <8336fap5qh.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1754 bytes --]

Yes, the problem goes away after reverting this commit.

Thanks Eli

Le jeu. 31 oct. 2019 à 00:18, Eli Zaretskii <eliz@gnu.org> a écrit :

> severity 37097 normal
> merge 37986 37097
> thanks
>
> > From: Sébastien Chapuis <sebastien@chapu.is>
> > Date: Wed, 30 Oct 2019 17:00:00 +0800
> >
> > $ git clone --recursive git://git.savannah.gnu.org/emacs.git
> > $ cd emacs && ./autogen.sh
> > $ mkdir build && cd build
> > $ ../configure --prefix=/opt/emacs-git --with-modules --with-xwidgets
> --with-imagemagick
> > $ make install
> > $ /opt/emacs-git/bin/emacs --fg-daemon -Q
> >
> > Open another terminal (terminal #2):
> > $ /opt/emacs-git/bin/emacsclient -n -c BIG_FILE.txt
> > the command doesn't return and no frame is opened.
> > On the terminal #1, there is this output:
> >
> > ```
> > Warning: due to a long standing Gtk+ bug
> > https://gitlab.gnome.org/GNOME/gtk/issues/221
> > Emacs might crash when run in daemon mode and the X11 connection is
> unexpectedly lost.
> > Using an Emacs configured with --with-x-toolkit=lucid does not have this
> problem.
> > Starting Emacs daemon.
> > File BIG_FILE.txt is large (11.9 MiB), really open? (y)es or (n)o or
> (l)iterally
> > File BIG_FILE.txt is large (11.9 MiB), really open? (y)es or (n)o or
> (l)iterally
> > ```
> >
> > Open a 3rd terminal (terminal #3):
> > $ /opt/emacs-git/bin/emacsclient -n -c
> > A new frame is opened with this message in the minibuffer:
> > `File BIG_FILE.txt is large (11.9 MiB), really open? (y)es or (n)o or
> (l)iterally`
> > If I type `y`, a new frame is opened (from terminal #2) with the file
> BIG_FILE.txt in its buffer.
>
> Thanks.  Can you see if the problem goes away if you revert commit
> 49fc040?
>

[-- Attachment #2: Type: text/html, Size: 2456 bytes --]

  reply	other threads:[~2019-11-01 13:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30  9:00 bug#37986: emacsclient doesn't open a frame when waiting for input in the minibuffer Sébastien Chapuis
2019-10-30 16:17 ` Eli Zaretskii
2019-11-01 13:35   ` Sébastien Chapuis [this message]
2019-11-01 13:43     ` Eli Zaretskii
2019-11-07 17:18       ` Eli Zaretskii
2019-11-08  5:25         ` Sébastien Chapuis
2019-11-08  6:55           ` 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=CAN2Hsvx7Pmf1BaGSE36zcO21BpZgX28mvTGWwK3m2iOOqW2Ujg@mail.gmail.com \
    --to=sebastien@chapu.is \
    --cc=37986@debbugs.gnu.org \
    --cc=eliz@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 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).