all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 34763@debbugs.gnu.org
Subject: bug#34763: 27.0.50; url-retrieve-synchronously misbehaves inside eldoc-documentation-function
Date: Thu, 04 Apr 2019 17:36:30 +0300	[thread overview]
Message-ID: <83lg0pdehd.fsf@gnu.org> (raw)
In-Reply-To: <c5b3e3a8-ec84-a436-8ff1-fb8e3552d842@yandex.ru> (message from Dmitry Gutov on Thu, 4 Apr 2019 16:29:24 +0300)

> Cc: 34763@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Thu, 4 Apr 2019 16:29:24 +0300
> 
> On 04.04.2019 16:04, Eli Zaretskii wrote:
> > If that's the intent, why does it need to explicitly quit in Lisp?
> > Just letting the code leave the form where inhibit-quit is non-nil
> > will let Emacs quit at the first opportunity, with no need for any
> > Lisp code for that.
> 
> Because accept-process-output doesn't abort on user input?

It doesn't?  Are you sure?  Or are you talking about calling
accept-process-output with inhibit-quit non-nil?

> And url-retrieve-synchronously calls it with 1 second timeout (which
> is a fairly long wait).

That could be dealt with by making the timeout shorter.

> 2. I wonder if there are cases where some part of the asynchronous code 
> takes too long, where it should be allowed to be aborted by the user 
> right away. Meaning when url-retrieve is used, not 
> url-retrieve-synchronously.

I always thought that C-g aborts accept-process-output.





  reply	other threads:[~2019-04-04 14:36 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
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 [this message]
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=83lg0pdehd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34763@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    /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.