From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 26986@debbugs.gnu.org
Subject: bug#26986: 26.0.50; Unsafe recovery should be off by default in batch mode
Date: Thu, 18 May 2017 20:26:13 +0000 [thread overview]
Message-ID: <CAArVCkR1NEySsWXLR5DDy4hgeAkrL=d=QEFbRUHzizMO0MzO5w@mail.gmail.com> (raw)
In-Reply-To: <83mvaa3pyd.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
Eli Zaretskii <eliz@gnu.org> schrieb am Do., 18. Mai 2017 um 21:50 Uhr:
> > From: Philipp <p.stephani2@gmail.com>
> > Date: Thu, 18 May 2017 21:44:22 +0200
> >
> > In batch mode there will usually be no long-lived buffers with
> > non-recoverable contents, therefore the reasoning for
> > `attempt-stack-overflow-recovery' and
> > `attempt-orderly-shutdown-on-fatal-signal' being t doesn't apply. This
> > means that these variables should be nil by default in batch mode.
>
> I see your point, but what are the arguments for changing their values
> in batch mode? IOW, what advantages will this give us?
>
When debugging Emacs internals or running unit tests, setting these
variables to nil will cause obvious and clear failures instead of silent
recovery attempts.
[-- Attachment #2: Type: text/html, Size: 1171 bytes --]
next prev parent reply other threads:[~2017-05-18 20:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 19:44 bug#26986: 26.0.50; Unsafe recovery should be off by default in batch mode Philipp
2017-05-18 19:49 ` Eli Zaretskii
2017-05-18 20:26 ` Philipp Stephani [this message]
2017-05-18 20:38 ` Eli Zaretskii
2017-05-27 12:06 ` Philipp Stephani
2017-05-27 13:31 ` Philipp Stephani
2017-05-27 13:39 ` Eli Zaretskii
2019-09-29 2:48 ` Stefan Kangas
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='CAArVCkR1NEySsWXLR5DDy4hgeAkrL=d=QEFbRUHzizMO0MzO5w@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=26986@debbugs.gnu.org \
--cc=eliz@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).