From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: htl10@users.sourceforge.net,
Hin-Tak Leung <hintak.leung@gmail.com>,
25203@debbugs.gnu.org
Subject: bug#25203: 25.1; crash during message, infinite recursion
Date: Thu, 15 Dec 2016 11:11:38 -0500 [thread overview]
Message-ID: <CAM-tV-9uW-hyd5BihmarjEeS41c3D=Y4aK=Dutre7rv+=cQpRQ@mail.gmail.com> (raw)
In-Reply-To: <83fulp9oft.fsf@gnu.org>
On Thu, Dec 15, 2016 at 10:55 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
> If someone is going to argue that Lisp code should never crash Emacs,
> then I can see the following alternatives:
>
> 1. Inhibit messages while calling pre-write-conversion.
> 2. Signal an error when pre-write-conversion is called recursively.
>
> I think none of these is a good idea, as they disallow perfectly valid
> use cases which don't hit this problem. The 2nd one is also error
> prone in its naïve implementation, and too complex IMO in non-naïve
> ones.
Shouldn't max-specdl or max-lisp-eval-depth be catching too deep
recursive calls?
next prev parent reply other threads:[~2016-12-15 16:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <955842899.6288681.1481820009426.ref@mail.yahoo.com>
2016-12-15 0:04 ` bug#25203: 25.1; crash during message, infinite recursion Hin-Tak Leung
2016-12-15 5:29 ` Werner LEMBERG
2016-12-15 15:55 ` Eli Zaretskii
2016-12-15 16:11 ` Noam Postavsky [this message]
2016-12-15 16:57 ` Eli Zaretskii
2016-12-15 16:48 ` Werner LEMBERG
2016-12-16 8:55 ` Eli Zaretskii
2016-12-16 9:08 ` Werner LEMBERG
2016-12-16 10:48 ` Eli Zaretskii
2016-12-15 16:40 ` Hin-Tak Leung
2016-12-15 22:57 ` bug#25203: [cjk] Fwd: HELP with emacs 25.1 and cjk-enc.el Hin-Tak Leung
2016-12-16 8:02 ` Eli Zaretskii
2016-12-16 9:28 ` Andreas Schwab
2016-12-16 10:48 ` Eli Zaretskii
2016-12-15 23:02 ` Hin-Tak Leung
2016-12-16 8:04 ` Eli Zaretskii
2016-12-16 9:00 ` Werner LEMBERG
2016-12-16 14:18 ` Hin-Tak Leung
2016-12-16 14:34 ` bug#25203: 25.1; crash during message, infinite recursion Hin-Tak Leung
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='CAM-tV-9uW-hyd5BihmarjEeS41c3D=Y4aK=Dutre7rv+=cQpRQ@mail.gmail.com' \
--to=npostavs@users.sourceforge.net \
--cc=25203@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=hintak.leung@gmail.com \
--cc=htl10@users.sourceforge.net \
/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).