all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: 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 05:30:11 +0300	[thread overview]
Message-ID: <83y1j3o158.fsf@gnu.org> (raw)
In-Reply-To: <m2lef35sov.fsf@z1k.dev> (message from Yikai Zhao on Wed, 26 Jul 2023 10:10:08 +0800)

> From: Yikai Zhao <yikai@z1k.dev>
> Date: Wed, 26 Jul 2023 10:10:08 +0800
> 
> 
> After updating to recent master version of emacs, emacsclient would
> block for an extra 2 seconds when some error is raised from command.

That's deliberate: we want to allow the user to see the error message.
It is not a bug.

> Why it affects me:
> 
> I bind some keyboard shortcut globally to a script to move either from
> emacs window or i3wm window. It does something like this:
> 
>    emacsclient -e '(windmove-right)' || i3-msg focus right
> 
> It rely on the behavior that, if I'm currently in the rightmost emacs
> buffer, '(windmove-right)' would return an error and fallback to use
> i3-msg to move to another frame. With this bug I mentioned, it would
> introduce 2-second delay on this action.

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.

Sorry.





  reply	other threads:[~2023-07-26  2:30 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 [this message]
2023-07-26 15:50   ` Yikai Zhao
2023-07-26 15:58     ` Eli Zaretskii
2023-07-26 18:07   ` Jim Porter
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=83y1j3o158.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64866@debbugs.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.