all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Sat, 27 May 2017 13:31:30 +0000	[thread overview]
Message-ID: <CAArVCkQV5DjZhmLscQ+QFDbe9xHDZqFWLTk_w40PLjmPx-GR2w@mail.gmail.com> (raw)
In-Reply-To: <CAArVCkQi7rUFeC0BkE+ZCCN+c3Q+0cu9-YhZ7JrFS81Lm9o+cg@mail.gmail.com>

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

  reply	other threads:[~2017-05-27 13:31 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
2017-05-18 20:38     ` Eli Zaretskii
2017-05-27 12:06       ` Philipp Stephani
2017-05-27 13:31         ` Philipp Stephani [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAArVCkQV5DjZhmLscQ+QFDbe9xHDZqFWLTk_w40PLjmPx-GR2w@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 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.