From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 22493@debbugs.gnu.org
Subject: bug#22493: 25.1.50; open-gnutls-stream doesn't respect :nowait, so the connections are synchronous
Date: Mon, 01 Feb 2016 20:50:17 +0200 [thread overview]
Message-ID: <83bn801d06.fsf@gnu.org> (raw)
In-Reply-To: <87egcx13kc.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 01 Feb 2016 05:01:55 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 22493@debbugs.gnu.org
> Date: Mon, 01 Feb 2016 05:01:55 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > There's no such thing in Emacs as an idle thread.
>
> Sorry; I meant the idle loop.
A sentinel indeed starts when Emacs is idle, but once it kicks in, it
runs to completion, and Emacs cannot do anything else while it does.
So if the user presses a key a millisecond after the sentinel is
invoked and starts the GnuTLS negotiation procedure, the user will
still have to wait.
So once again I must ask what exactly do we gain with these changes.
If all we want is to make the GnuTLS negotiation wait until Emacs is
idle, we could run it from an idle timer, which would have been
simpler, and won't require us to have a process object in a strange
limbo state that cannot be communicated through.
next prev parent reply other threads:[~2016-02-01 18:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 4:00 bug#22493: 25.1.50; open-gnutls-stream doesn't respect :nowait, so the connections are synchronous Lars Ingebrigtsen
2016-01-30 4:45 ` Lars Ingebrigtsen
2016-01-30 9:21 ` Eli Zaretskii
2016-01-30 22:55 ` Lars Ingebrigtsen
2016-01-31 0:40 ` Lars Ingebrigtsen
2016-01-31 1:10 ` Lars Ingebrigtsen
2016-01-31 16:00 ` Eli Zaretskii
2016-01-31 15:59 ` Eli Zaretskii
2016-01-31 23:17 ` Lars Ingebrigtsen
2016-02-01 2:41 ` Lars Ingebrigtsen
2016-02-01 3:41 ` Eli Zaretskii
2016-02-01 4:01 ` Lars Ingebrigtsen
2016-02-01 18:50 ` Eli Zaretskii [this message]
2016-02-02 1:43 ` Lars Ingebrigtsen
2016-02-02 16:10 ` Eli Zaretskii
2016-02-03 1:10 ` Lars Ingebrigtsen
2016-02-03 1:58 ` Lars Ingebrigtsen
2016-02-03 15:52 ` Eli Zaretskii
2016-02-04 2:47 ` Lars Ingebrigtsen
2016-02-04 16:39 ` Eli Zaretskii
2016-02-05 2:36 ` Lars Ingebrigtsen
2016-02-05 7:24 ` Eli Zaretskii
2016-02-05 7:34 ` Lars Ingebrigtsen
2016-02-05 9:18 ` Eli Zaretskii
2016-02-06 3:03 ` Lars Ingebrigtsen
2016-02-06 7:51 ` Eli Zaretskii
2016-02-06 7:57 ` Lars Ingebrigtsen
2016-02-03 15:51 ` Eli Zaretskii
2016-02-04 2:59 ` Lars Ingebrigtsen
2016-01-31 15:57 ` Eli Zaretskii
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=83bn801d06.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22493@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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.