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: Tue, 08 Dec 2020 14:51:23 +0100 [thread overview]
Message-ID: <878sa8l82s.fsf@gnus.org> (raw)
In-Reply-To: <83blf58qfm.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 07 Dec 2020 19:41:01 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> I'm not sure what sit-for you're referring to here.
>
> Not sit-for, sit_for. This one:
>
> tem0 = sit_for (Vecho_keystrokes, 1, 1);
>
> You did say we are stuck there for the duration of that 1 sec, didn't
> you? So I'm saying that the problem might be that the connection from
> the client doesn't stop sit_for's waiting, and one possible solution
> is to arrange it to do so.
>
> Does that make sense?
Not immediately. :-)
I though that that variable was for echoing unfinished (i.e., partial)
keystrokes? When doing an `M-x', there no timeout for displaying the
`M-x', so it's not clear to me why that should influence anything.
In any case, I thought I could experiment with changing the timeout to
confirm (or not) this hypothesis, but... I can't reproduce the reported
behaviour any more: "emacsclient -c" now pops up without any delay, even
if the server is in a `M-x'. :-/
Is anybody else seeing this behaviour with the current trunk?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2020-12-08 13:51 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
2020-12-07 17:41 ` Eli Zaretskii
2020-12-08 13:51 ` Lars Ingebrigtsen [this message]
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=878sa8l82s.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.