From: Jean Louis <bugs@gnu.support>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 47556@debbugs.gnu.org
Subject: bug#47556: "really open? (y)es or (n)o or (l)iterally" vs. emacsclient -n
Date: Fri, 2 Apr 2021 09:27:29 +0300 [thread overview]
Message-ID: <YGa5UeMPWqa50GaM@protected.localdomain> (raw)
In-Reply-To: <87czvdwrx3.5.fsf@jidanni.org>
* 積丹尼 Dan Jacobson <jidanni@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/
next prev parent reply other threads:[~2021-04-02 6:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 22:39 bug#47556: "really open? (y)es or (n)o or (l)iterally" vs. emacsclient -n 積丹尼 Dan Jacobson
2021-04-02 6:19 ` Jean Louis
2021-04-02 6:27 ` Jean Louis [this message]
2021-04-02 7:06 ` 積丹尼 Dan Jacobson
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=YGa5UeMPWqa50GaM@protected.localdomain \
--to=bugs@gnu.support \
--cc=47556@debbugs.gnu.org \
--cc=jidanni@jidanni.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).