[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Crash recovery strategies
From: |
Daniel Colascione |
Subject: |
Re: Crash recovery strategies |
Date: |
Sun, 3 Jan 2016 15:29:44 -0800 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 |
On 01/03/2016 03:27 PM, John Wiegley wrote:
>>>>>> Paul Eggert <address@hidden> writes:
>
>> So although it'd be fine to have async-signal-safe autosave as an option, as
>> a user I'd like to also retain the option for Emacs to keep doing the same
>> old unsafe stuff that it's been doing for decades, at least until after we
>> get in-the-field experience with the new approach.
>
> Agreed. There should absolutely be an option to retain the unsafe behavior,
> since at the very least it can be useful to have Emacs stick around while
> exploring the behavior of a bug in situ. So we won't delete the longjmp code,
> we just might change the default behavior to something more consistent with
> safer practices.
>
> Also completely agree on the in-the-field experience part. I'm not even sure
> we'll change the default behavior right away; we might give it a few releases
> to see how it goes, and to hear back from people who've decided to turn it on.
More generally, how do we feel about automatically sending crash reports
to the FSF? Of course, we'd send reports stripped of personally
identifiable information, as is standard practice.
signature.asc
Description: OpenPGP digital signature
- Re: Crash recovery strategies, (continued)
- Re: Crash recovery strategies, Eli Zaretskii, 2016/01/04
- Re: Crash recovery strategies, Daniel Colascione, 2016/01/04
- Re: Crash recovery strategies, Eli Zaretskii, 2016/01/04
- Re: Crash recovery strategies, Paul Eggert, 2016/01/03
- Re: Crash recovery strategies, Daniel Colascione, 2016/01/03
- Re: Crash recovery strategies, John Wiegley, 2016/01/03
- Re: Crash recovery strategies, Paul Eggert, 2016/01/03
- Re: Crash recovery strategies, John Wiegley, 2016/01/03
- Re: Crash recovery strategies,
Daniel Colascione <=
- Sending automatic crash reports to the FSF (was: Crash recovery strategies), John Wiegley, 2016/01/03
- Re: Sending automatic crash reports to the FSF, Daniel Colascione, 2016/01/03
- Re: Sending automatic crash reports to the FSF, John Wiegley, 2016/01/03
- Re: Sending automatic crash reports to the FSF, Daniel Colascione, 2016/01/03
- RE: Crash recovery strategies, Drew Adams, 2016/01/03
- Re: Crash recovery strategies (was: Dynamic modules: MODULE_HANDLE_SIGNALS etc.), Eli Zaretskii, 2016/01/04
- Re: Crash recovery strategies, Daniel Colascione, 2016/01/04
- Re: Crash recovery strategies, Eli Zaretskii, 2016/01/04
- Re: Crash recovery strategies, Richard Stallman, 2016/01/04
- Re: Crash recovery strategies, Eli Zaretskii, 2016/01/05