* bug#37986: emacsclient doesn't open a frame when waiting for input in the minibuffer
@ 2019-10-30 9:00 Sébastien Chapuis
2019-10-30 16:17 ` Eli Zaretskii
0 siblings, 1 reply; 7+ messages in thread
From: Sébastien Chapuis @ 2019-10-30 9:00 UTC (permalink / raw)
To: 37986
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
This bug occurs on emacs master branch but it doesn't with emacs 26.2
Steps to reproduce:
terminal #1:
$ 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.
Let me know if you need more details.
Thanks,
Sebastien Chapuis.
[-- Attachment #2: Type: text/html, Size: 1937 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#37986: emacsclient doesn't open a frame when waiting for input in the minibuffer
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
0 siblings, 1 reply; 7+ messages in thread
From: Eli Zaretskii @ 2019-10-30 16:17 UTC (permalink / raw)
To: Sébastien Chapuis; +Cc: 37986
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?
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#37986: emacsclient doesn't open a frame when waiting for input in the minibuffer
2019-10-30 16:17 ` Eli Zaretskii
@ 2019-11-01 13:35 ` Sébastien Chapuis
2019-11-01 13:43 ` Eli Zaretskii
0 siblings, 1 reply; 7+ messages in thread
From: Sébastien Chapuis @ 2019-11-01 13:35 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 37986
[-- 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 --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#37986: emacsclient doesn't open a frame when waiting for input in the minibuffer
2019-11-01 13:35 ` Sébastien Chapuis
@ 2019-11-01 13:43 ` Eli Zaretskii
2019-11-07 17:18 ` Eli Zaretskii
0 siblings, 1 reply; 7+ messages in thread
From: Eli Zaretskii @ 2019-11-01 13:43 UTC (permalink / raw)
To: Sébastien Chapuis; +Cc: 37986
> From: Sébastien Chapuis <sebastien@chapu.is>
> Date: Fri, 1 Nov 2019 21:35:24 +0800
> Cc: 37986@debbugs.gnu.org
>
> Yes, the problem goes away after reverting this commit.
OK, thanks for testing.
I'm going to revert that commit in a couple of days, unless a better
solution comes to mind. We tried to fix a minor aesthetic problem,
and instead got ourself several much more grave ones.
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#37986: emacsclient doesn't open a frame when waiting for input in the minibuffer
2019-11-01 13:43 ` Eli Zaretskii
@ 2019-11-07 17:18 ` Eli Zaretskii
2019-11-08 5:25 ` Sébastien Chapuis
0 siblings, 1 reply; 7+ messages in thread
From: Eli Zaretskii @ 2019-11-07 17:18 UTC (permalink / raw)
To: sebastien; +Cc: 37986
> Date: Fri, 01 Nov 2019 15:43:25 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 37986@debbugs.gnu.org
>
> > From: Sébastien Chapuis <sebastien@chapu.is>
> > Date: Fri, 1 Nov 2019 21:35:24 +0800
> > Cc: 37986@debbugs.gnu.org
> >
> > Yes, the problem goes away after reverting this commit.
>
> OK, thanks for testing.
>
> I'm going to revert that commit in a couple of days, unless a better
> solution comes to mind. We tried to fix a minor aesthetic problem,
> and instead got ourself several much more grave ones.
Done. Please see that this issue is now resolved.
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#37986: emacsclient doesn't open a frame when waiting for input in the minibuffer
2019-11-07 17:18 ` Eli Zaretskii
@ 2019-11-08 5:25 ` Sébastien Chapuis
2019-11-08 6:55 ` Eli Zaretskii
0 siblings, 1 reply; 7+ messages in thread
From: Sébastien Chapuis @ 2019-11-08 5:25 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 37986
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
Yes it works now.
Thank you !
Le ven. 8 nov. 2019 à 01:19, Eli Zaretskii <eliz@gnu.org> a écrit :
> > Date: Fri, 01 Nov 2019 15:43:25 +0200
> > From: Eli Zaretskii <eliz@gnu.org>
> > Cc: 37986@debbugs.gnu.org
> >
> > > From: Sébastien Chapuis <sebastien@chapu.is>
> > > Date: Fri, 1 Nov 2019 21:35:24 +0800
> > > Cc: 37986@debbugs.gnu.org
> > >
> > > Yes, the problem goes away after reverting this commit.
> >
> > OK, thanks for testing.
> >
> > I'm going to revert that commit in a couple of days, unless a better
> > solution comes to mind. We tried to fix a minor aesthetic problem,
> > and instead got ourself several much more grave ones.
>
> Done. Please see that this issue is now resolved.
>
[-- Attachment #2: Type: text/html, Size: 1364 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#37986: emacsclient doesn't open a frame when waiting for input in the minibuffer
2019-11-08 5:25 ` Sébastien Chapuis
@ 2019-11-08 6:55 ` Eli Zaretskii
0 siblings, 0 replies; 7+ messages in thread
From: Eli Zaretskii @ 2019-11-08 6:55 UTC (permalink / raw)
To: Sébastien Chapuis; +Cc: 37986-done
> From: Sébastien Chapuis <sebastien@chapu.is>
> Date: Fri, 8 Nov 2019 13:25:18 +0800
> Cc: 37986@debbugs.gnu.org
>
> Yes it works now.
Thanks for testing, closing the bug.
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2019-11-08 6:55 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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
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).