From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: emacs-lock-unlockable-modes should default to nil Date: Sat, 07 Jul 2018 12:54:03 +0300 Message-ID: <83bmbjjrr8.fsf@gnu.org> References: NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1530957157 13281 195.159.176.226 (7 Jul 2018 09:52:37 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 7 Jul 2018 09:52:37 +0000 (UTC) Cc: lekktu@gmail.com, emacs-devel@gnu.org To: Tino Calancha Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jul 07 11:52:33 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fbjtI-0003Lh-Oy for ged-emacs-devel@m.gmane.org; Sat, 07 Jul 2018 11:52:32 +0200 Original-Received: from localhost ([::1]:32959 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fbjvP-0003qD-U6 for ged-emacs-devel@m.gmane.org; Sat, 07 Jul 2018 05:54:43 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33169) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fbjuo-0003q7-TI for emacs-devel@gnu.org; Sat, 07 Jul 2018 05:54:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fbjuo-0001BR-3t for emacs-devel@gnu.org; Sat, 07 Jul 2018 05:54:06 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:50779) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fbjuj-00019l-AN; Sat, 07 Jul 2018 05:54:01 -0400 Original-Received: from [176.228.60.248] (port=2828 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fbjuh-0003QA-AT; Sat, 07 Jul 2018 05:54:00 -0400 In-reply-to: (message from Tino Calancha on Sat, 30 Jun 2018 16:40:45 +0900 (JST)) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:227042 Archived-At: > From: Tino Calancha > Date: Sat, 30 Jun 2018 16:40:45 +0900 (JST) > Cc: Juanma Barranquero , > Tino Calancha > > I see the comment in the source code: the current value is due > to compatibility with older versions. > > I was bitten today with this. I first thought it was a > bug; then, I realized is the result of a default setting. > > Many users would assume that their buffers are secured once they > turn on this minor-mode, overlooking that this option does exist. > I think the value nil is a better default to support such expectations. The current value was set 7 years ago and released in Emacs 24.1 6 years ago. I'm not sure this is long enough for such a radical change. In any case, it is not a good situation that the doc string of emacs-lock-mode doesn't even mention emacs-lock-unlockable-modes, so users have no hope of learning about this variable's critical importance unless they read the code. So as the first step towards perhaps changing the default in the future, I added references to this variable to relevant doc strings. Thanks.