From: "Göktuğ Kayaalp" <self@gkayaalp.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29550@debbugs.gnu.org
Subject: bug#29550: 27.0.50; `not-modified' should be disabled by default
Date: Tue, 05 Dec 2017 12:49:08 +0300 [thread overview]
Message-ID: <ygmr2s9v71n.fsf@gkayaalp.com> (raw)
In-Reply-To: <83fu8ryxhq.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 04 Dec 2017 05:37:21 +0200")
On 2017-12-04 05:37 +02, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Göktuğ Kayaalp <self@gkayaalp.com>
>> Date: Mon, 04 Dec 2017 02:19:45 +0300
>>
>> I suggest that the command ‘not-modified’, bound by default to ‘M-~’, be
>> disabled by default, as it can cause data loss and is easily triggered
>> accidentally
>
> FWIW, I use this command many times every day, with no data loss.
> Just one data point.
>
There probably are some disabled commands that each of us use all the
time. ‘erase-buffer’, ‘upcase-region’ and ‘downcase-region’ are some
for me. I think ‘not-modified’ is at least as risky as those commands
given it can be hit accidentally, maybe more easily, as I've said
previously, for someone using a keyboard where tilde is easily
(mis-)typed (in my British layout keyboard it's just to the left of the
big return button: jkl;' then #/~), and indeed would be «confusing for
beginners», quoting the disabled command buffer. Also, from Glenn
Morris' message in this thread, there seems to be two other times in
history where a similar request to mine has been made. If my patch is
refused I'll just have it disabled in my config, but I truly think that
this command, bound to a non-prefixed binding in the global map, is
potentially confusing and dangerous for who doesn't already know it,
beginner or not; if we have upcase/downcase-region disabled, this should
be disabled too.
--
İ. Göktuğ Kayaalp <http://www.gkayaalp.com/>
024C 30DD 597D 142B 49AC
40EB 465C D949 B101 2427
next prev parent reply other threads:[~2017-12-05 9:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 23:19 bug#29550: 27.0.50; `not-modified' should be disabled by default Göktuğ Kayaalp
2017-12-04 3:37 ` Eli Zaretskii
2017-12-04 17:58 ` Glenn Morris
2017-12-05 10:06 ` Göktuğ Kayaalp
2018-04-15 19:06 ` Lars Ingebrigtsen
2017-12-05 9:49 ` Göktuğ Kayaalp [this message]
2019-09-29 0:06 ` Stefan Kangas
2019-09-29 7:20 ` Eli Zaretskii
2019-09-29 7:35 ` Stefan Kangas
2019-09-29 7:59 ` Eli Zaretskii
2019-09-29 8:01 ` Lars Ingebrigtsen
2019-09-29 8:28 ` Eli Zaretskii
2019-09-29 8:58 ` Andreas Schwab
2019-09-29 10:05 ` Lars Ingebrigtsen
2019-10-04 18:38 ` Göktuğ Kayaalp
2019-10-04 19:40 ` Eli Zaretskii
2020-08-10 14:02 ` Lars Ingebrigtsen
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=ygmr2s9v71n.fsf@gkayaalp.com \
--to=self@gkayaalp.com \
--cc=29550@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.