GNU bug report logs - #47556
"really open? (y)es or (n)o or (l)iterally" vs. emacsclient -n

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 47556 in the body.
You can then email your comments to 47556 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: bug-gnu-emacs <at> gnu.org
Subject: "really open? (y)es or (n)o or (l)iterally" vs. emacsclient -n
Date: Fri, 02 Apr 2021 06:39:36 +0800

$ emacs -Q --maximized -eval '(server-start)'&
$ emacsclient -n big.jpg
big.jpg is large (14.5 MiB), really open? (y)es or (n)o or (l)iterally
Alas in this case our y, n, or l's are not being read by the mini-buffer!

And if we indeed switch to emacs and type "n", the question doesn't go
away yet, until we type something into the *scratch* buffer.

If we instead use --fullscreen, we can't even see the mini-buffer (at
least in icewm.)

emacs-version "27.1"

Message #8 received at 47556 <at> debbugs.gnu.org (full text, mbox):

From: Jean Louis <bugs <at> gnu.support>
To: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Cc: 47556 <at> debbugs.gnu.org
Subject: Re: bug#47556: "really open? (y)es or (n)o or (l)iterally" vs.
 emacsclient -n
Date: Fri, 2 Apr 2021 09:19:33 +0300

* 積丹尼 Dan Jacobson <jidanni <at> jidanni.org> [2021-04-02 03:00]:
> $ emacs -Q --maximized -eval '(server-start)'&

I like when Emacs starts maximized. That is why I have put this in
~/.emacs.d/early-init.el:

(add-to-list 'default-frame-alist '(fullscreen . maximized))

That way each time it starts maximized.

> $ emacsclient -n big.jpg
> big.jpg is large (14.5 MiB), really open? (y)es or (n)o or (l)iterally
> Alas in this case our y, n, or l's are not being read by the
> mini-buffer!

I do not observe this in Emacs development version. I have tested this
in Emacs development version and when I do that, I am shown the frame
that I have started and the minibuffer and question in the minibuffer,
and I could answer with "y" and see the large file.

Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

Sign an open letter in support of Richard M. Stallman
https://rms-support-letter.github.io/

Message #11 received at 47556 <at> debbugs.gnu.org (full text, mbox):

From: Jean Louis <bugs <at> gnu.support>
To: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Cc: 47556 <at> debbugs.gnu.org
Subject: Re: bug#47556: "really open? (y)es or (n)o or (l)iterally" vs.
 emacsclient -n
Date: Fri, 2 Apr 2021 09:27:29 +0300

* 積丹尼 Dan Jacobson <jidanni <at> jidanni.org> [2021-04-02 03:00]:
> $ emacs -Q --maximized -eval '(server-start)'&
> $ emacsclient -n big.jpg
> big.jpg is large (14.5 MiB), really open? (y)es or (n)o or (l)iterally
> Alas in this case our y, n, or l's are not being read by the mini-buffer!
> 
> And if we indeed switch to emacs and type "n", the question doesn't go
> away yet, until we type something into the *scratch* buffer.
> 
> If we instead use --fullscreen, we can't even see the mini-buffer (at
> least in icewm.)
> 
> emacs-version "27.1"

I am also using IceWM. I have tested in Emacs development version more
of this, as you said --fullscreen, and I did not observe that
behavior. I have tried answering Y and N and all is fine.

So it is read by minibuffer in Emacs development version.

It is true that message remains longer in minibuffer, this disturbs me
sometimes.

My hope is that my IceWm settings do not interfere with this testing,
as I have in ~/.icewm/window this below inhibiting the title bar, I
don't think it interferes.

emacs.dTitleBar: 0
emacsclient.dTitleBar: 0


Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

Sign an open letter in support of Richard M. Stallman
https://rms-support-letter.github.io/

Message #14 received at 47556 <at> debbugs.gnu.org (full text, mbox):

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: Jean Louis <bugs <at> gnu.support>
Cc: 47556 <at> debbugs.gnu.org
Subject: Re: bug#47556: "really open? (y)es or (n)o or (l)iterally" vs.
 emacsclient -n
Date: Fri, 02 Apr 2021 15:06:57 +0800

>>>>> "JL" == Jean Louis <bugs <at> gnu.support> writes:
JL> It is true that message remains longer in minibuffer, this disturbs me
JL> sometimes.

OK then just somebody fix that only please,
as all the icemw stuff might be due to our icewm init files,
and newer fixes with icewm upstream with various versions.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.