From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Turning on savehist-mode by default Date: Sun, 19 Nov 2023 10:23:09 +0200 Message-ID: <83cyw6kv82.fsf@gnu.org> References: <87wmufm7r7.fsf@catern.com> <87fs12jkik.fsf@yahoo.com> <83il5ykyki.fsf@gnu.org> <877cmejj8e.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11845"; mail-complaints-to="usenet@ciao.gmane.io" Cc: sbaugh@catern.com, emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Nov 19 09:23:55 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1r4d5v-0002qu-Gl for ged-emacs-devel@m.gmane-mx.org; Sun, 19 Nov 2023 09:23:55 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r4d5W-00083C-Rf; Sun, 19 Nov 2023 03:23:30 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r4d5U-00082n-PA for emacs-devel@gnu.org; Sun, 19 Nov 2023 03:23:28 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r4d5U-0000im-Br; Sun, 19 Nov 2023 03:23:28 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=tmr33f6PK+GJqLB2e3cOxGCl4K3bb/C54GaB/rmEbWk=; b=SQqYDIFPKPLP iV0RHIOd74Opgh+PDjdg0YIe1iu7jb7tMR+VMkNo/wQHycbCFo+8dhOo5caYnSsQMp4EZuC+W+ewy fPTgaZoZipIBDRkAK5lQQgJqnxnlNbZaIioheiDLBSLSC+2NZx67pgJqAHglkC4KWA3v1EzNW5/y2 4LePUUVOIuQsRQ08B9XvNRifNZ8TmINIQfGTnghL84p6ZJdxhCi5j6L5Jqh7DkGNL+JvPx7jXMFc6 Zrb5azt7He9rh2RheDZELAmEPMrjaeBcqeccGQAdgrTz4wxibibtzuK5vxZ0GzJNKkal8z4Q2wCFU UtJt+3YR2ENcfiFxWGzx6g==; In-Reply-To: <877cmejj8e.fsf@yahoo.com> (message from Po Lu on Sun, 19 Nov 2023 15:27:29 +0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:312956 Archived-At: > From: Po Lu > Cc: sbaugh@catern.com, emacs-devel@gnu.org > Date: Sun, 19 Nov 2023 15:27:29 +0800 > > Eli Zaretskii writes: > > > I disagree that there's a disadvantage in that, let alone a grave one. > > I'm using desktop.el, which does both of the above, for many years, > > and have yet to see any problems with that. > > I know this is a disadvantage for one subset of our users, because I > often witness them kill Emacs in precisely the fashion I mentioned > earlier. And that's if the lock files strewn everywhere belonging to > long-dead Emacs sessions aren't evidence enough. People are free to shoot themselves in the foot, but they shouldn't then come back to use crying that it hurts. If someone kills Emacs with a fatal signal, they should not be surprised that their files are sometimes corrupted. Anyway, IME, the files are usable in the next session even if the previous session was terminated abnormally, like when AC power goes down. I don't remember even a single instance of having unusable files saved by a timer or kill-emacs-hook even though my sessions are not always terminated normally.