all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: emacs-lock-unlockable-modes should default to nil
Date: Sat, 07 Jul 2018 12:54:03 +0300	[thread overview]
Message-ID: <83bmbjjrr8.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1806301626400.15639@calancha-pc.dy.bbexcite.jp> (message from Tino Calancha on Sat, 30 Jun 2018 16:40:45 +0900 (JST))

> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Sat, 30 Jun 2018 16:40:45 +0900 (JST)
> Cc: Juanma Barranquero <lekktu@gmail.com>,
> 	Tino Calancha <tino.calancha@gmail.com>
> 
> 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.



  reply	other threads:[~2018-07-07  9:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30  7:40 emacs-lock-unlockable-modes should default to nil Tino Calancha
2018-07-07  9:54 ` Eli Zaretskii [this message]
2018-07-07 10:23   ` Tino Calancha

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83bmbjjrr8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=tino.calancha@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.