From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34763@debbugs.gnu.org
Subject: bug#34763: 27.0.50; url-retrieve-synchronously misbehaves inside eldoc-documentation-function
Date: Tue, 12 Mar 2019 17:02:31 +0200 [thread overview]
Message-ID: <54096647-4d80-bb67-6be5-bd48bfa4cc6c@yandex.ru> (raw)
In-Reply-To: <787f765a-42f4-40d0-3b78-e751f546fe6c@yandex.ru>
Some further investigation follows.
I've checked out the revision before the one where eldoc started to use
while-no-input (6d898918980be4cb29a182ecde7f8e1f95a08462) and repeated
the scenario.
Predictably, Emacs was considerably less responsive, lots of pauses
waiting for the replies from the remote server.
Also predictably, no "Transfer interrupted" messages until I press C-g.
But I still reach the state where Emacs seemingly just freezes with
"Contacting host: www.google.com:80" in the echo area, and even faster
than with the current Emacs master (within the first 10-20 seconds).
I can abort that with tapping C-g, see that "Transfer interrupted"
message (Emacs still frozen), and then tapping C-g again to see "eldoc
error: (error Interrupted!)", wait a second, and see "Quit".
The message log is only slightly different: it consistently says:
"error in process sentinel: url-http-end-of-document-sentinel: Transfer
interrupted!"
Whereas previously, I mostly seen other sentinels mentioned here.
After Emacs freezes this way once and I C-g out of it, similarly to the
original problem description, any subsequent call to silly-eldoc freezes
right away. Calling url-retrieve-synchronously from eval-expression,
meanwhile, works (although kind of slowly).
This reminds me strongly of a problem with my third-party package
reported by several people, which I never managed to cleanly reproduce:
https://github.com/dgutov/robe/issues/105
Also tried this in Emacs 25.2, the scenario reproduces almost exactly.
next prev parent reply other threads:[~2019-03-12 15:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 21:34 bug#34763: 27.0.50; url-retrieve-synchronously misbehaves inside eldoc-documentation-function Dmitry Gutov
2019-03-11 0:18 ` Dmitry Gutov
2019-03-11 14:30 ` Eli Zaretskii
2019-03-12 9:08 ` Dmitry Gutov
2019-03-12 15:02 ` Dmitry Gutov [this message]
2019-03-12 17:18 ` Eli Zaretskii
2019-03-12 17:44 ` Dmitry Gutov
2019-03-12 18:00 ` Eli Zaretskii
2019-03-12 20:05 ` Dmitry Gutov
2019-03-13 16:49 ` Eli Zaretskii
2019-03-15 14:24 ` Dmitry Gutov
2019-03-15 15:47 ` Eli Zaretskii
2019-03-15 16:07 ` Dmitry Gutov
2019-03-15 14:29 ` Dmitry Gutov
2019-03-15 15:49 ` Eli Zaretskii
2019-04-03 23:37 ` Dmitry Gutov
2019-04-04 13:04 ` Eli Zaretskii
2019-04-04 13:29 ` Dmitry Gutov
2019-04-04 14:36 ` Eli Zaretskii
2019-04-05 0:29 ` Dmitry Gutov
2019-04-05 6:14 ` Eli Zaretskii
2019-04-08 10:25 ` Dmitry Gutov
2019-04-08 15:20 ` Eli Zaretskii
2019-04-08 16:42 ` Dmitry Gutov
2019-04-08 17:13 ` Eli Zaretskii
2019-04-09 0:48 ` Dmitry Gutov
2019-04-09 6:34 ` Eli Zaretskii
2019-04-10 1:44 ` Dmitry Gutov
2019-04-10 15:46 ` Eli Zaretskii
2019-04-11 1:03 ` Dmitry Gutov
2019-04-11 7:59 ` Andreas Schwab
2019-04-11 13:08 ` Dmitry Gutov
2019-04-11 15:08 ` Dmitry Gutov
2019-04-11 16:22 ` Eli Zaretskii
2019-04-11 16:31 ` Dmitry Gutov
2019-04-13 0:44 ` Dmitry Gutov
2019-05-15 5:16 ` Lars Ingebrigtsen
2019-05-21 1:02 ` Dmitry Gutov
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=54096647-4d80-bb67-6be5-bd48bfa4cc6c@yandex.ru \
--to=dgutov@yandex.ru \
--cc=34763@debbugs.gnu.org \
--cc=eliz@gnu.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.