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:29:44 -0800 Message-ID: <5689AEE8.7030707@dancol.org> References: <83mvu1x6t3.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="fFeje6h1x9bHpDDxlahgVJd6A1dUu2DcF" X-Trace: ger.gmane.org 1451863809 32430 80.91.229.3 (3 Jan 2016 23:30:09 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 3 Jan 2016 23:30:09 +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:30:00 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 1aFs63-0008CP-Ph for ged-emacs-devel@m.gmane.org; Mon, 04 Jan 2016 00:29:59 +0100 Original-Received: from localhost ([::1]:43224 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFs63-0003xZ-8Q for ged-emacs-devel@m.gmane.org; Sun, 03 Jan 2016 18:29:59 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40125) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFs5z-0003v3-MU for Emacs-devel@gnu.org; Sun, 03 Jan 2016 18:29:56 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aFs5v-0007xw-L8 for Emacs-devel@gnu.org; Sun, 03 Jan 2016 18:29:55 -0500 Original-Received: from dancol.org ([2600:3c01::f03c:91ff:fedf:adf3]:40662) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFs5v-0007wn-Cf; Sun, 03 Jan 2016 18:29:51 -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=jInzkoRiyr0WNcjjtY2/Ycw+zEPD4jvnu+7Yl70WN4A=; b=h23JD3fqitVxMelMdV66DRaTKgcGzgVjnWb2ESPsHNhuiZpHBk8yaq5enzCD6ymqwzse1obMVeiMebqccFazZUrGBfjnkm4uJksuGyrbldbY3S6UTdR6Ewj6BRGjRaUZ89S4h51I/5yzD4SNFwTyPHFhsAKUeMaVKyA+czvLF/YDFqNKKtg2h1nYyjy/lBvS6HxHVnVnADqH06gag4ktOS+IXDnhyEIJLdp/GKMWO3i7Ovj5dORFU9h3skQzJORZfTKgIGmWhD5rpq4mO2yldUYB7c7nneZMpKLgU/YeK4BtekpO24MWTkgFCjchBW0yKgwbVKKiwph4xEnyk/dHFg==; 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 1aFs5u-0007zQ-Tf; Sun, 03 Jan 2016 15:29:51 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 In-Reply-To: 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:197529 Archived-At: This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --fFeje6h1x9bHpDDxlahgVJd6A1dUu2DcF Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 01/03/2016 03:27 PM, John Wiegley wrote: >>>>>> Paul Eggert writes: >=20 >> So although it'd be fine to have async-signal-safe autosave as an opti= on, 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 afte= r we >> get in-the-field experience with the new approach. >=20 > Agreed. There should absolutely be an option to retain the unsafe behav= ior, > since at the very least it can be useful to have Emacs stick around whi= le > 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. >=20 > 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 re= leases > 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. --fFeje6h1x9bHpDDxlahgVJd6A1dUu2DcF 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 iQIcBAEBCAAGBQJWia7oAAoJEN4WImmbpWBln04QAJrtXfqsJ+0VqEgjiidrjEo1 cT7tMtIYp/7HtHWIEWlEmdltVMZ8eUt7AMy3nkazZ3etT5y/ah5/YeF+3H7L7jHw dvCI/9QpQNpxBHmyxTHf9Z3/Ifk7/D0k3g8ZYDovyKlXleJWMXfnvmZZRMqctCp0 nN2RYcNARKuNQrxm3wfXFEH/UjgDxCiXwi5txBYOQn9SfQ/NdcoVLxoZiMiOwuGD luwkT/S72rxjQh3KAs1BP+XLLJ/ojDlzg9xUtWgYjEk8Ivo4KpS0voOjlHE+dzt6 8ubrIzdyqgrlaCDNtkGtQhD4SecTvgdfdNjroPh+2rdsTYQGtjZZd3c8Ay5kMKBM HoS/Ji3/AHz64wWeJ1tsQ7NEkgh36Xu2iYSNaqUztQuIPNVEbvizvYBaGlUE3Z4Q sEVyf9mYQWG2tRKlrGR/DPe3+TVHwdM20IMqaCgPmaTXQ869YBfgs9HL9L+j8fwi /1NqSRqSQ1IZKXptmSHzb2wnM1FpUjsKMB34CUMooYm6i7/16Ver20Lk+7J4IVxj bMcBMxIe436NXYpCy7De/yuQcVJsNPqjkN7eDaM5TAJ4XBg9fNSZxERewYEpgRlJ eKvYV/VXuD0op6Ec+fwiI0wZuoah4HS5Nf5PXN4CkxBQbJmmRcLaDhwyQIdoeNcx MMbAPwEojt5O1pQKj93u =8eYX -----END PGP SIGNATURE----- --fFeje6h1x9bHpDDxlahgVJd6A1dUu2DcF--