From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Yikai Zhao <yikai@z1k.dev>
Cc: 64866@debbugs.gnu.org
Subject: bug#64866: 30.0.50; Emacsclient block for 2 seconds when error is raised from command
Date: Wed, 26 Jul 2023 11:07:24 -0700 [thread overview]
Message-ID: <f691212b-8636-d4bd-23ad-f73d79195761@gmail.com> (raw)
In-Reply-To: <83y1j3o158.fsf@gnu.org>
On 7/25/2023 7:30 PM, Eli Zaretskii wrote:
> I don't think your quite special use case is a reason good enough to
> prevent users from seeing error messages. An error message that
> cannot be read is useless.
In this case, the user *can* see the error though: it's printed in the
terminal that they called `emacsclient -e '(error "oops")'` from. Even
without the 2 second delay, I don't think there would be any loss of
information to the user (at least not that I can see).
I've actually seen a related issue come up elsewhere: in our regression
tests. When testing programmable completion in Eshell, I had to let-bind
'minibuffer-message-timeout' to 0 to prevent the 2 second delay, which
occurred even in batch mode. (See
'em-cmpl-test/variable-ref-completion/directory' in
"test/lisp/eshell/em-cmpl-tests.el".) I'm not sure why this delay is
present in batch mode. (Going back to the original bug report, I'd
consider 'emacsclient -e blah' to be analogous to batch mode.)
Strangely, I tried running this and I still see a 2 second delay:
emacsclient -e '(let ((minibuffer-message-timeout 0)) (error "oops"))'
I'm not sure why that doesn't work...
next prev parent reply other threads:[~2023-07-26 18:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 2:10 bug#64866: 30.0.50; Emacsclient block for 2 seconds when error is raised from command Yikai Zhao
2023-07-26 2:30 ` Eli Zaretskii
2023-07-26 15:50 ` Yikai Zhao
2023-07-26 15:58 ` Eli Zaretskii
2023-07-26 18:07 ` Jim Porter [this message]
2023-07-26 18:48 ` Eli Zaretskii
2023-07-26 19:48 ` Jim Porter
2023-07-27 4:48 ` Eli Zaretskii
2023-07-27 5:34 ` Jim Porter
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f691212b-8636-d4bd-23ad-f73d79195761@gmail.com \
--to=jporterbugs@gmail.com \
--cc=64866@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=yikai@z1k.dev \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.