From: Jean Louis <bugs@gnu.support>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 37352@debbugs.gnu.org
Subject: bug#37352: 27.0.50; recursive-edit aborts on elisp error after evaluation
Date: Sun, 22 Sep 2019 14:57:44 +0200 [thread overview]
Message-ID: <20190922125743.GJ5996@protected.rcdrun.com> (raw)
In-Reply-To: <87tv9665t8.fsf@gnus.org>
* Lars Ingebrigtsen <larsi@gnus.org> [2019-09-20 23:01]:
> Jean Louis <bugs@gnu.support> writes:
>
> > Please see the attached picture. I have turned off debug on error
> > before evaluating (jnjn) non-existing function.
>
> The picture (sent in a separate email) showed a backtrace, so you do
> have debug-on-error switched on -- perhaps via
> eval-expression-debug-on-error? (It's a separate setting when you do
> M-:, which is rather confusing.)
Exactl that. If I turn off eval-expression-debug-on-error, then there
is no interruption of recursive-edit and I can continue editing.
That is probably better defined bug.
The eval-expression-debug-on-error when T or NIL shall not interrupt
the recursive-edit if there is error in evaluation. The debug window
could be finalized or abandoned, and then the old window shall
continue processing the text edited.
If you think that is not a bug, let me know. Then I can implement it
in my function and avoid the problem.
Jean
next prev parent reply other threads:[~2019-09-22 12:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 7:41 bug#37352: 27.0.50; recursive-edit aborts on elisp error after evaluation Jean Louis
2019-09-20 18:30 ` Lars Ingebrigtsen
2019-09-20 19:09 ` Jean Louis
2019-09-20 21:01 ` Lars Ingebrigtsen
2019-09-22 12:57 ` Jean Louis [this message]
2019-09-22 13:00 ` Lars Ingebrigtsen
2019-09-22 13:04 ` Jean Louis
2019-09-22 13:49 ` Lars Ingebrigtsen
2019-09-22 16:14 ` Drew Adams
2019-09-22 16:39 ` Noam Postavsky
2019-09-22 16:55 ` Drew Adams
2019-09-22 16:59 ` Eli Zaretskii
2019-09-22 17:54 ` Andreas Schwab
2019-09-22 18:20 ` Eli Zaretskii
2019-09-23 10:18 ` Lars Ingebrigtsen
2019-09-23 12:43 ` Noam Postavsky
2019-09-23 14:01 ` Lars Ingebrigtsen
2019-09-23 14:14 ` Andreas Schwab
2019-09-25 8:11 ` Eli Zaretskii
2019-09-25 13:09 ` Lars Ingebrigtsen
2019-09-22 16:58 ` 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=20190922125743.GJ5996@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=37352@debbugs.gnu.org \
--cc=larsi@gnus.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).