From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: monnier@iro.umontreal.ca, 45117@debbugs.gnu.org
Subject: bug#45117: 28.0.50; process-send-string mysteriously exiting non-locally when called from timer
Date: Thu, 10 Dec 2020 22:14:01 +0200 [thread overview]
Message-ID: <83r1nx2zcm.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm52LkKTK+s+ftmfqkFhdpt1zNYL79MzEZHLp031xOW=sNA@mail.gmail.com> (message from João Távora on Thu, 10 Dec 2020 19:58:12 +0000)
> From: João Távora <joaotavora@gmail.com>
> Date: Thu, 10 Dec 2020 19:58:12 +0000
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 45117@debbugs.gnu.org
>
> > I think that's the wrong question. The right question is how probable
> > is it that the user presses C-g to abort a timer function that just
> > happens to run at this very moment. I think the answer is "extremely
> > improbable". It is much more probable that C-g was meant for
> > something else, some activity that is much more evident to the user.
> > Like getting out of the minibuffer after deciding that the command
> > does not need to be invoked after all, for example.
>
> I see. Yes it makes sense. But Stefan is arguing that some "special" timer
> functions should be abortable by mere input.
That makes sense mainly for idle timers. Or for timer functions that
take a lot of time to execute (something that generally shouldn't
happen in the first place). But while-no-input cannot abort its
caller, so as long as the body of while-no-input can handle being
interrupted, that is okay.
> And that changes thoses odds considerably. But at the same time, it
> doesn't change the fact, as you well put it, that that input is
> _not_ meant for the timer function.
I think if a timer function should be interruptible by input, that
function should itself call while-no-input. It is not the job of
outside code to interrupt bad timers by aborting them by these
measures.
next prev parent reply other threads:[~2020-12-10 20:14 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 11:44 bug#45117: 28.0.50; process-send-string mysteriously exiting non-locally when called from timer João Távora
2020-12-08 15:39 ` Eli Zaretskii
2020-12-08 15:56 ` João Távora
2020-12-08 17:01 ` Eli Zaretskii
2020-12-08 17:05 ` João Távora
2020-12-09 11:24 ` João Távora
2020-12-09 15:33 ` Eli Zaretskii
2020-12-10 15:00 ` João Távora
2020-12-10 15:23 ` Eli Zaretskii
2020-12-10 16:15 ` João Távora
2020-12-10 16:29 ` João Távora
2020-12-10 17:20 ` Dmitry Gutov
2020-12-10 17:51 ` Stefan Monnier
2020-12-10 18:05 ` João Távora
2020-12-10 18:37 ` Stefan Monnier
2020-12-10 18:48 ` Eli Zaretskii
2020-12-10 18:50 ` João Távora
2020-12-10 19:44 ` Eli Zaretskii
2020-12-10 19:47 ` João Távora
2020-12-10 19:55 ` Eli Zaretskii
2020-12-10 19:58 ` João Távora
2020-12-10 20:14 ` Eli Zaretskii [this message]
2020-12-10 20:15 ` João Távora
2020-12-10 20:37 ` Dmitry Gutov
2020-12-10 19:46 ` Stefan Monnier
2020-12-10 20:12 ` João Távora
2020-12-10 20:43 ` Stefan Monnier
2020-12-10 20:55 ` Dmitry Gutov
2020-12-10 22:48 ` Stefan Monnier
2020-12-10 21:16 ` João Távora
2020-12-10 22:58 ` João Távora
2020-12-11 7:31 ` Eli Zaretskii
2020-12-11 14:31 ` Stefan Monnier
2020-12-11 14:40 ` Eli Zaretskii
2020-12-11 14:43 ` João Távora
2020-12-11 14:41 ` João Távora
2020-12-11 14:50 ` Stefan Monnier
2020-12-13 23:19 ` João Távora
2020-12-14 0:35 ` Stefan Monnier
2020-12-10 16:41 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r1nx2zcm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45117@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).