From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 38035@debbugs.gnu.org, rms@gnu.org
Subject: bug#38035: 27.0.50; Trivial errors in process filters can render Emacs unusable
Date: Thu, 14 Nov 2019 10:58:48 +0200 [thread overview]
Message-ID: <838soi96lz.fsf@gnu.org> (raw)
In-Reply-To: <87h83czt41.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 09 Nov 2019 21:34:38 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: rms@gnu.org, 38035@debbugs.gnu.org
> Date: Sat, 09 Nov 2019 21:34:38 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Maybe we should do the same with timer functions, indeed.
>
> And post-command-hook and all the other errors?
IMO no, because post-command-hook isn't asynchronous.
> >> I just think that Emacs should behave consistently.
> >
> > If doing the same with timers will contribute to that consistency, I
> > don't object. I just think that we shouldn't remove an old feature
> > because of a single accident that should be quite rare.
>
> What do you mean by "single accident"?
The one that you cited, and which started this.
next prev parent reply other threads:[~2019-11-14 8:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 17:53 bug#38035: 27.0.50; Trivial errors in process filters can render Emacs unusable Lars Ingebrigtsen
2019-11-02 18:36 ` Eli Zaretskii
2019-11-02 18:38 ` Lars Ingebrigtsen
2019-11-02 18:40 ` Eli Zaretskii
2019-11-03 13:21 ` Richard Stallman
2019-11-03 14:52 ` Lars Ingebrigtsen
2019-11-03 15:51 ` Eli Zaretskii
2019-11-03 16:39 ` Lars Ingebrigtsen
2019-11-03 17:03 ` Eli Zaretskii
2019-11-08 20:42 ` Lars Ingebrigtsen
2019-11-08 20:50 ` Eli Zaretskii
2019-11-08 20:54 ` Lars Ingebrigtsen
2019-11-09 6:24 ` Eli Zaretskii
2019-11-09 20:34 ` Lars Ingebrigtsen
2019-11-14 8:58 ` Eli Zaretskii [this message]
2019-11-14 9:56 ` Lars Ingebrigtsen
2019-11-14 14:13 ` Eli Zaretskii
2019-11-15 7:53 ` Lars Ingebrigtsen
2019-11-04 3:55 ` Richard Stallman
2021-12-02 11:55 ` Lars Ingebrigtsen
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=838soi96lz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=38035@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rms@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 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).