From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19945@debbugs.gnu.org, noe.rubinstein@gmail.com
Subject: bug#19945: emacsclient confused by active minibuffer
Date: Mon, 07 Dec 2020 14:17:12 +0100 [thread overview]
Message-ID: <87y2i9kb6v.fsf@gnus.org> (raw)
In-Reply-To: <83v9df9idz.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 06 Dec 2020 15:24:56 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> My question was whether this wait is on purpose (to notify the user that
>> we're ending the M-x), or whether it's a bug.
>
> It's neither, AFAIU. It's just that sit_for is not interrupted by the
> client attempting to connect (like it would by keyboard input, for
> example). If I'm right, then TRT, IMO, would be to arrange for it to
> be interrupted in this case.
>
> (The wait in this case is to provide echo for the key sequence when
> the user stops typing for a while, but cease waiting immediately when
> new input arrives.)
I'm not sure what sit-for you're referring to here.
The user hits
`M-x'
which enters a recursive edit, and the "M-x" is displayed immediately.
Then, sometime much later, the user says "emacsclient -nw". Then there
is a one-second delay, and then the Emacs server filter executes the
actions the client asked for.
Now, the recursive edit is exited by `server-goto-toplevel', but
instrumenting all of this (i.e., the server filter function) is giving
me inconsistent results -- that is, I can't actually pinpoint where in
the code the wait is happening... perhaps because some redisplay is
inhibited somewhere? I'm not sure; it's somewhat frustrating...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-12-07 13:17 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
2020-12-06 12:55 ` Lars Ingebrigtsen
2020-12-06 13:24 ` Eli Zaretskii
2020-12-07 13:17 ` Lars Ingebrigtsen [this message]
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=87y2i9kb6v.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=19945@debbugs.gnu.org \
--cc=eliz@gnu.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.