From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daniel Colascione Newsgroups: gmane.emacs.devel Subject: Re: Crash recovery strategies Date: Sun, 3 Jan 2016 15:24:05 -0800 Message-ID: <5689AD95.6040200@dancol.org> References: <83mvu1x6t3.fsf@gnu.org> <5678D620.6070000@cs.ucla.edu> <83mvt2qxm1.fsf@gnu.org> <56797CD9.8010706@cs.ucla.edu> <8337uuqsux.fsf@gnu.org> <5679DC83.70405@cs.ucla.edu> <83oadhp2mj.fsf@gnu.org> <567AD556.6020202@cs.ucla.edu> <567AD766.3060608@dancol.org> <567B5DAB.2000900@cs.ucla.edu> <83fuyromig.fsf@gnu.org> <567C25B1.3020101@dancol.org> <56892FD6.8040708@dancol.org> <568988EE.3010205@dancol.org> <56899278.9000007@dancol.org> <56899EAC.1030408@dancol.org> <5689ACFC.5050407@cs.ucla.edu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="uEnkpWQ15Xx0jE2ihrNIodeQsuNjKKKG2" X-Trace: ger.gmane.org 1451863482 27750 80.91.229.3 (3 Jan 2016 23:24:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 3 Jan 2016 23:24:42 +0000 (UTC) To: Paul Eggert , Eli Zaretskii , Emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 04 00:24:33 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aFs0j-0003C2-O8 for ged-emacs-devel@m.gmane.org; Mon, 04 Jan 2016 00:24:29 +0100 Original-Received: from localhost ([::1]:43207 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFs0j-0000zp-2j for ged-emacs-devel@m.gmane.org; Sun, 03 Jan 2016 18:24:29 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38258) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFs0V-0000zT-Vm for Emacs-devel@gnu.org; Sun, 03 Jan 2016 18:24:16 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aFs0R-0006Vo-UK for Emacs-devel@gnu.org; Sun, 03 Jan 2016 18:24:15 -0500 Original-Received: from dancol.org ([2600:3c01::f03c:91ff:fedf:adf3]:40654) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFs0R-0006Vk-Nn; Sun, 03 Jan 2016 18:24:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dancol.org; s=x; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject; bh=6vdsXcOTPWbRoWsnbfUju3XC+9OtLcvQK7+wo2q6/xw=; b=FxDR2wexabUB6T1MVint3kysNO+YSSFU5EpxxWaokU7BUj/l/hh0vM/huH6cU+EZgTlnfYkrM9EGV4ohXtlruhOfMXzILO90it5j+njx+ATmQtQgzQEMoTyc81hmI3ZqFCV2EyNEO+rAlEFdMb7r0QZS0DUbGrH1NEd/V47Qyx3PalwVH+v4FHLJNdcMP22WkZ5YHzyx/aDT0pzb/+lTVrAxbxmDJOlwyzBfWbOpbl7R7gq1oR2IpPF9tTsxq2js1ru6EGSd+156GQrFiQZBXLhD0x5OCYKOemYHSPP5jQ2DZPJTITVT65Br35hqM4C0VSs0bq9cxOXzC3TvnT2Kpg==; Original-Received: from mobile-166-176-184-191.mycingular.net ([166.176.184.191] helo=[192.168.43.34]) by dancol.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84) (envelope-from ) id 1aFs0R-0007xX-9W; Sun, 03 Jan 2016 15:24:11 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 In-Reply-To: <5689ACFC.5050407@cs.ucla.edu> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2600:3c01::f03c:91ff:fedf:adf3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:197525 Archived-At: This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --uEnkpWQ15Xx0jE2ihrNIodeQsuNjKKKG2 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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. >=20 > 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 tha= t > state. So although it'd be fine to have async-signal-safe autosave as a= n > 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. --uEnkpWQ15Xx0jE2ihrNIodeQsuNjKKKG2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJWia2VAAoJEN4WImmbpWBlRCwP/2GucJ7mrNsEUCv+wXVzLut5 2VNM6dIuWHjC8SZBn1SQkWXZfkrJ/MaQXPcE3qDysfi/IjcdJJlPH2ARbDIICY10 4cfS0vcGW/WWV3A9P5aiY9ExqNXQmFBUtU08wwSPke4YpD9v+5FQ4VErx650HI1l naS0gnps3zMsd3TXArJaNNeJTn/AJyiwGBfzm+cx7rcX7TQb9swg4kk9WFGoNCbT r3P55Ivan+FOfKoLW11hLzhYfMCqZTGO35fFGn0RDrvd+k8p/rR0qkEsTuBiCFMm R2bqJG2R8Mzsa16XWfuyzgO3Nff9iTHKILJPKLi9vyNIqIHfONTgdU3z2gA0dJ7w pQ3zSXbXC5KXKz7Zks4j8J5tIXmP1HQx81PZgm7uJtesWTmKEJszBVmFhz2VaW8c CirzEsG2lQlEPH2ZSpdkMJbcOOGndkOmNIGuA7DWeQOO6TA2QMqnDN9c2FKbLLnJ U/jBaNZVEn37zWVh/2Zw2JW1Qy0is3BBmsUDAL81daEHN0NucBgCdFJChh6GVG1U ZjcgVsUSf03Srko/DYE2jHafCVCMrWCpGaCYpowE9JKskCPZefg6lbief7QOR15r kSfrfk0qlWFO32/XlVL8wZlxIqzaqMdnkSy0FliVJCN3MEeCZGFu0rtwP8X/aCDB 3sPQ9DcCiA4L+Bd+kdGJ =xpa/ -----END PGP SIGNATURE----- --uEnkpWQ15Xx0jE2ihrNIodeQsuNjKKKG2--