unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sebastian Urban <mrsebastianurban@gmail.com>
To: juri@linkov.net
Cc: 37447@debbugs.gnu.org
Subject: bug#37447: 26.3; Commands on <delete> and <backspace>
Date: Fri, 20 Sep 2019 10:17:38 +0200	[thread overview]
Message-ID: <8e473f5a-2582-7086-8bd8-da75c00607d5@gmail.com> (raw)
In-Reply-To: <f49e689b-ed08-646c-5fc4-da6316dd711b@gmail.com>

> Imagine many users using the same keys for years, and now
> they will start doing the opposite - a recipe for disaster.

And that's why I'm not proposing changing C-b/n/p/f to C-h/j/k/l.  But
these two cases (without C-S-<backspace>) I pointed out doesn't seem
very critical, moreover they look like a bug (with 'M-<delete>'
deleting backward instead of forward as 'M-d' does - 'C-d' does
similar thing do <delete>, so 'M-...' should also be similar) or like
a leftover from the past ('C-<backspace>') that could be reused for
something useful.

Also, there are "obsolete" functions that are removed after few
versions of Emacs, so why not do the same thing to key bindings?  They
don't change that often, so it won't be a revolution, right?  Keeping
old key bindings forever(?), especially when user can change them, is
rather strange - confusion among new users, less keys for new/other
commands, etc.  I think Emacs should have one default key per command,
older should be marked as "obsolete" and removed after 1 or 2 major
versions.

But, this is from perspective of a beginner, so...





  parent reply	other threads:[~2019-09-20  8:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-18 11:45 bug#37447: 26.3; Commands on <delete> and <backspace> Sebastian Urban
2019-09-18 12:39 ` Eli Zaretskii
2019-09-18 13:18   ` Sebastian Urban
2019-09-19 20:31     ` Juri Linkov
2019-09-19 21:17       ` Drew Adams
2019-09-19 21:59         ` Noam Postavsky
2019-09-19 22:13           ` Juri Linkov
2019-09-21 15:41             ` Dmitry Gutov
2019-09-20  8:17 ` Sebastian Urban [this message]
2019-09-20  8:36   ` Eli Zaretskii
2019-09-20  9:17     ` Sebastian Urban
2019-09-20  9:31       ` Eli Zaretskii
2019-09-20 10:32         ` Sebastian Urban
2019-09-20 12:46           ` Eli Zaretskii
2019-09-20 16:22             ` Sebastian Urban
  -- strict thread matches above, loose matches on Subject: below --
2017-11-24 19:12 bug#29430: 26.0.90; C-M-backspace is undefined Devon Sean McCullough
2017-11-24 19:28 ` Noam Postavsky
2022-03-23 13:30   ` bug#37447: 26.3; Commands on <delete> and <backspace> Lars Ingebrigtsen
2022-03-23 14:35     ` Drew Adams

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=8e473f5a-2582-7086-8bd8-da75c00607d5@gmail.com \
    --to=mrsebastianurban@gmail.com \
    --cc=37447@debbugs.gnu.org \
    --cc=juri@linkov.net \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).