bug#26986: 26.0.50; Unsafe recovery should be off by default in batch mode

bug#26986: 26.0.50; Unsafe recovery should be off by default in batch mode

[Philipp]

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.


In GNU Emacs 26.0.50 (build 85, x86_64-apple-darwin16.5.0, NS appkit-1504.82 Version 10.12.4 (Build 16E195))
 of 2017-05-18 built on p
Repository revision: 8deef1d6a7bf620abf4219b6471883381b817724
Windowing system distributor 'Apple', version 10.3.1504
Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.

Configured using:
 'configure --with-modules --without-xml2 --without-pop --with-mailutils
 --enable-gcc-warnings=warn-only --enable-checking
 --enable-check-lisp-object-type
 MAKEINFO=/usr/local/opt/texinfo/bin/makeinfo 'CFLAGS=-ggdb3 -O0''

Configured features:
RSVG DBUS NOTIFY ACL GNUTLS ZLIB TOOLKIT_SCROLL_BARS NS MODULES

Important settings:
  value of $LANG: de_DE.UTF-8
  locale-coding-system: utf-8-unix

Major mode: Lisp Interaction

Minor modes in effect:
  tooltip-mode: t
  global-eldoc-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Load-path shadows:
None found.

Features:
(shadow sort mail-extr emacsbug message subr-x puny seq byte-opt gv
bytecomp byte-compile cconv cl-loaddefs cl-lib dired dired-loaddefs
format-spec rfc822 mml easymenu mml-sec password-cache epa derived epg
epg-config gnus-util rmail rmail-loaddefs mm-decode mm-bodies mm-encode
mail-parse rfc2231 mailabbrev gmm-utils mailheader sendmail rfc2047
rfc2045 ietf-drums mm-util mail-prsvr mail-utils time-date tooltip eldoc
electric uniquify ediff-hook vc-hooks lisp-float-type mwheel term/ns-win
ns-win ucs-normalize mule-util term/common-win tool-bar dnd fontset
image regexp-opt fringe tabulated-list replace newcomment text-mode
elisp-mode lisp-mode prog-mode register page menu-bar rfn-eshadow
isearch timer select scroll-bar mouse jit-lock font-lock syntax facemenu
font-core term/tty-colors frame cl-generic cham georgian utf-8-lang
misc-lang vietnamese tibetan thai tai-viet lao korean japanese eucjp-ms
cp51932 hebrew greek romanian slovak czech european ethiopic indian
cyrillic chinese composite charscript charprop case-table epa-hook
jka-cmpr-hook help simple abbrev obarray minibuffer cl-preloaded nadvice
loaddefs button faces cus-face macroexp files text-properties overlay
sha1 md5 base64 format env code-pages mule custom widget
hashtable-print-readable backquote dbusbind kqueue cocoa ns multi-tty
make-network-process emacs)

Memory information:
((conses 16 204419 8753)
 (symbols 48 20017 2)
 (miscs 40 50 195)
 (strings 32 18042 5580)
 (string-bytes 1 589313)
 (vectors 16 35616)
 (vector-slots 8 703770 4113)
 (floats 8 48 68)
 (intervals 56 213 0)
 (buffers 976 11))

bug#26986: 26.0.50; Unsafe recovery should be off by default in batch mode

[Eli Zaretskii]

> 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?

bug#26986: 26.0.50; Unsafe recovery should be off by default in batch mode

[Philipp Stephani]

[-- 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 --]

bug#26986: 26.0.50; Unsafe recovery should be off by default in batch mode

[Eli Zaretskii]

> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Thu, 18 May 2017 20:26:13 +0000
> Cc: 26986@debbugs.gnu.org
> 
>  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. 

OK, but the batch mode is not used only for debugging or testing.
Perhaps we should change the values in these two cases.

bug#26986: 26.0.50; Unsafe recovery should be off by default in batch mode

[Philipp Stephani]

[-- Attachment #1: Type: text/plain, Size: 823 bytes --]

Eli Zaretskii <eliz@gnu.org> schrieb am Do., 18. Mai 2017 um 22:39 Uhr:

> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Thu, 18 May 2017 20:26:13 +0000
> > Cc: 26986@debbugs.gnu.org
> >
> >  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.
>
> OK, but the batch mode is not used only for debugging or testing.
> Perhaps we should change the values in these two cases.
>

That would be a good start. However, I still think these should be off in
batch mode by default; batch mode is very unlikely to be used for
circumstances where they could be useful.

[-- Attachment #2: Type: text/html, Size: 1274 bytes --]

bug#26986: 26.0.50; Unsafe recovery should be off by default in batch mode

[Philipp Stephani]

[-- Attachment #1: Type: text/plain, Size: 820 bytes --]

Philipp Stephani <p.stephani2@gmail.com> schrieb am Sa., 27. Mai 2017 um
14:06 Uhr:

> Eli Zaretskii <eliz@gnu.org> schrieb am Do., 18. Mai 2017 um 22:39 Uhr:
>
>> > From: Philipp Stephani <p.stephani2@gmail.com>
>> > Date: Thu, 18 May 2017 20:26:13 +0000
>> > Cc: 26986@debbugs.gnu.org
>> >
>> >  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.
>>
>> OK, but the batch mode is not used only for debugging or testing.
>> Perhaps we should change the values in these two cases.
>>
>
> That would be a good start.
>

I've installed commit ebe0bdae9d for this.

[-- Attachment #2: Type: text/html, Size: 1597 bytes --]

bug#26986: 26.0.50; Unsafe recovery should be off by default in batch mode

[Eli Zaretskii]

> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Sat, 27 May 2017 12:06:52 +0000
> Cc: 26986@debbugs.gnu.org
> 
>  OK, but the batch mode is not used only for debugging or testing.
>  Perhaps we should change the values in these two cases.
> 
> That would be a good start. However, I still think these should be off in batch mode by default; batch mode is
> very unlikely to be used for circumstances where they could be useful. 

Batch mode is frequently used to test or present problems that happen
in interactive sessions, so I'd like to avoid making the batch mode
too different from the rest.

bug#26986: 26.0.50; Unsafe recovery should be off by default in batch mode

[Stefan Kangas]

tags 26986 + wontfix
close 26986
quit

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Philipp Stephani <p.stephani2@gmail.com>
>> Date: Sat, 27 May 2017 12:06:52 +0000
>> Cc: 26986@debbugs.gnu.org
>>
>>  OK, but the batch mode is not used only for debugging or testing.
>>  Perhaps we should change the values in these two cases.
>>
>> That would be a good start. However, I still think these should be off in batch mode by default; batch mode is
>> very unlikely to be used for circumstances where they could be useful.
>
> Batch mode is frequently used to test or present problems that happen
> in interactive sessions, so I'd like to avoid making the batch mode
> too different from the rest.

I understand Eli's message here as wontfix.  I'm closing this bug report
as such.

If anyone disagrees, feel free to reopen.

Best regards,
Stefan Kangas