From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: larsi@gnus.org, 38035@debbugs.gnu.org
Subject: bug#38035: 27.0.50; Trivial errors in process filters can render Emacs unusable
Date: Sun, 03 Nov 2019 17:51:30 +0200 [thread overview]
Message-ID: <83ftj5hsal.fsf@gnu.org> (raw)
In-Reply-To: <E1iRFoe-0001I4-7D@fencepost.gnu.org> (message from Richard Stallman on Sun, 03 Nov 2019 08:21:12 -0500)
> From: Richard Stallman <rms@gnu.org>
> Date: Sun, 03 Nov 2019 08:21:12 -0500
> Cc: 38035@debbugs.gnu.org
>
> The special code to make errors in filters visible is an important
> feature. It prevents confusion, whereby users don't understand
> what is failing because they don't see the error messages.
>
> It also makes possible, as you've pointed out, one more way you can
> screw yourself with a perverse Lisp program -- but is it worth trying
> to fix that?
The current idea for a fix is to let the error be displayed several
times, until and unless it is clear that the error is repeatedly
signaled with a very high frequency, and if so, disable the filter for
that process.
I think this strikes the right balance between showing the error to
users and still leaving Emacs in a usable state.
next prev parent reply other threads:[~2019-11-03 15:51 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ftj5hsal.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 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.