[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:24:05 -0800 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 |
On 01/03/2016 03:21 PM, Paul Eggert wrote:
> John Wiegley wrote:
>> I'd like to know what others think (maybe they are ignoring this
>> thread now,
>> so I've changed the subject). But I feel like there is some
>> convergence now.
>
> I didn't understand all the details of the proposal. That being said,
> I'm not sure I like the idea of losing my Emacs session merely because
> some regular expression got too long. Sure, Emacs would create a bunch
> of autosave files that I can recover file data from, but if my session
> has been going for hours or days it'll have quite a bit of state that
> isn't in any buffer associated with a file, and I'd rather not lose that
> state. 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.
As I've mentioned elsewhere, I'm perfectly happy making the regular
expression code a special case, since we own it and know what it does. I
agree that Emacs absolutely shouldn't crash on any Lisp input to
re-search-forward, looking-at, etc.
signature.asc
Description: OpenPGP digital signature
- Re: Crash recovery strategies, (continued)
- Re: Crash recovery strategies, John Wiegley, 2016/01/03
- Re: Crash recovery strategies, John Wiegley, 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, 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, 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 <=
- 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, 2016/01/03
- 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