From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 19945@debbugs.gnu.org, noe.rubinstein@gmail.com
Subject: bug#19945: emacsclient confused by active minibuffer
Date: Fri, 04 Dec 2020 13:49:03 +0200 [thread overview]
Message-ID: <83mtyteqq8.fsf@gnu.org> (raw)
In-Reply-To: <87tut1nbk9.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 04 Dec 2020 10:51:50 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 19945@debbugs.gnu.org, noe.rubinstein@gmail.com
> Date: Fri, 04 Dec 2020 10:51:50 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> But the first point still stands -- terminal 2 displays *scratch* first,
> >> and then, one second later, switches to *foo* -- presumably there's
> >> something timing out the `M-x' thing?
> >>
> >> Does anybody have any insight into what might be happening here?
> >
> > We wait for echo-keystrokes seconds, I presume.
>
> Yes, that seems to be it -- but why is emacsclient doing that instead of
> ending the interaction immediately?
It isn't emacsclient that's doing this. Remember: emacsclient just
sends a command to Emacs via a socket; processing of that command and
displaying the results on the frame's display is done by the server,
i.e. by Emacs.
So it's Emacs that's waiting, probably inside sit_for.
next prev parent reply other threads:[~2020-12-04 11:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 8:49 bug#19945: emacsclient confused by active minibuffer Noé Rubinstein
2020-12-03 11:44 ` Lars Ingebrigtsen
2020-12-03 15:32 ` Eli Zaretskii
2020-12-04 9:51 ` Lars Ingebrigtsen
2020-12-04 11:49 ` Eli Zaretskii [this message]
2020-12-06 12:55 ` Lars Ingebrigtsen
2020-12-06 13:24 ` Eli Zaretskii
2020-12-07 13:17 ` Lars Ingebrigtsen
2020-12-07 17:41 ` Eli Zaretskii
2020-12-08 13:51 ` Lars Ingebrigtsen
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=83mtyteqq8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19945@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=noe.rubinstein@gmail.com \
/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.