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 19:44:04 +0200 [thread overview]
Message-ID: <8f7ae869-2e94-5535-f16f-476348036dc2@yandex.ru> (raw)
In-Reply-To: <831s3c3ta8.fsf@gnu.org>
On 12.03.2019 19:18, Eli Zaretskii wrote:
>> Cc: 34763@debbugs.gnu.org
>> From: Dmitry Gutov <dgutov@yandex.ru>
>> Date: Tue, 12 Mar 2019 11:08:06 +0200
>>
>> On 11.03.2019 16:30, Eli Zaretskii wrote:
>>
>>> Does it help to replace this:
>>>
>>> (defsubst url-http-debug (&rest args)
>>> (if quit-flag
>>>
>>> with this:
>>>
>>> (defsubst url-http-debug (&rest args)
>>> (if (eq quit-flag t)
>>>
>>> in url-http.el?
>>
>> No change, unfortunately. I double-checked.
>
> Crystal ball says there _was_ in fact a change: the error message text
> has changed slightly.
I'm sorry, you are right. The text did change.
> The below should fix both; please see if it does, and also whether it
> fixes your original real-life use case.
The patch does away with the first part of the complaint: no "Transfer
interrupted" or "Interrupted" messages anymore. Thanks!
The HTTP requests do take longer and longer times to complete, though.
After enough typing, the 10th request never seems to complete. I can
monitor that with changing the function's definition to
(defun silly-eldoc ()
(dotimes (i 10)
(url-retrieve-synchronously "http://www.google.com")
(message "try %i" i))
"done")
and watching the Messages buffer.
The counter fairly quickly reaches 0, but rarely goes past 3, and almost
never past 5 (now that I've been calling that eldoc function for several
minutes, albeit with big pauses).
M-x list-processes shows 12 lines with very similar contents.
I don't know whether having 10 requests to the same URL counts as a
real-life case, though.
next prev parent reply other threads:[~2019-03-12 17:44 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
2019-03-12 17:18 ` Eli Zaretskii
2019-03-12 17:44 ` Dmitry Gutov [this message]
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=8f7ae869-2e94-5535-f16f-476348036dc2@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.