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