From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "larsi@gnus.org" <larsi@gnus.org>,
"npostavs@users.sourceforge.net" <npostavs@users.sourceforge.net>,
"Emacs-Hacker2017@jovi.net" <Emacs-Hacker2017@jovi.net>,
"37447@debbugs.gnu.org" <37447@debbugs.gnu.org>,
"29430@debbugs.gnu.org" <29430@debbugs.gnu.org>
Subject: bug#37447: bug#29430: bug#37447: 26.3; Commands on <delete> and <backspace>
Date: Thu, 24 Mar 2022 15:16:32 +0000 [thread overview]
Message-ID: <SJ0PR10MB54884498410B3EF8D6ECB6ABF3199@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83zglfdf3o.fsf@gnu.org>
> > > > [C-M-delete] is problematic for MS Windows, no?
> > >
> > > Problematic in what sense?
> >
> > By default, at least, it's grabbed by Windows.
>
> But that hasn't changed just because Emacs now has a binding to that
> key, has it? IOW, whatever problems Windows users had or didn't have
> before the change, they still either have or don't have.
Yes, of course. But without binding it by default
users are less likely to suffer the gotcha.
Just mentioning that that binding can be a problem
for some Windows users. If you feel it's important
to bind it by default, so be it.
next prev parent reply other threads:[~2022-03-24 15:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2017-11-24 20:35 ` Devon Sean McCullough
2017-11-25 23:14 ` Richard Stallman
2017-11-29 18:02 ` Devon Sean McCullough
2022-03-23 13:30 ` bug#37447: 26.3; Commands on <delete> and <backspace> Lars Ingebrigtsen
2022-03-23 14:35 ` Drew Adams
2022-03-23 14:56 ` bug#37447: bug#29430: " Eli Zaretskii
2022-03-23 20:49 ` bug#29430: " Drew Adams
2022-03-24 6:44 ` Eli Zaretskii
2022-03-24 15:16 ` Drew Adams [this message]
2022-03-24 15:27 ` bug#37447: " Eli Zaretskii
2022-03-24 15:51 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR10MB54884498410B3EF8D6ECB6ABF3199@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=29430@debbugs.gnu.org \
--cc=37447@debbugs.gnu.org \
--cc=Emacs-Hacker2017@jovi.net \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=npostavs@users.sourceforge.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 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.