From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: theophilusx@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Keybinding styles (was: [External] : Re: Gitlab Migration)
Date: Sat, 04 Sep 2021 18:50:22 +0300 [thread overview]
Message-ID: <831r64wda9.fsf@gnu.org> (raw)
In-Reply-To: <90277C17-5C44-411F-A43A-EFCA9C0B7345@gmail.com> (message from Yuan Fu on Sat, 4 Sep 2021 08:44:02 -0700)
> From: Yuan Fu <casouri@gmail.com>
> Date: Sat, 4 Sep 2021 08:44:02 -0700
> Cc: Tim Cross <theophilusx@gmail.com>, emacs-devel@gnu.org
>
> On Mac I never had the problem because C-x/c/v and other system shortcuts are bound to the Command key, not Control. So I can use Emacs bindings with Control and system shortcuts with Command. Can we do the same in Windows and Linux? We can use the win key as Control for Emacs—seems that was where the Control key back in the day anyway.
Win+C, Win+X, etc. are hardly natural for MS-Windows users.
But let's first think about users of GNU/Linux, okay?
next prev parent reply other threads:[~2021-09-04 15:50 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 18:00 [External] : Re: Gitlab Migration Drew Adams
2021-09-03 20:06 ` Stefan Kangas
2021-09-03 22:49 ` Stefan Monnier
2021-09-04 2:00 ` Tim Cross
2021-09-04 13:26 ` Keybinding styles (was: [External] : Re: Gitlab Migration) Stefan Monnier
2021-09-04 13:39 ` Dmitry Gutov
2021-09-04 14:25 ` Keybinding styles Stefan Monnier
2021-09-04 15:44 ` Keybinding styles (was: [External] : Re: Gitlab Migration) Yuan Fu
2021-09-04 15:50 ` Eli Zaretskii [this message]
2021-09-04 15:55 ` Drew Adams
2021-09-04 16:07 ` Yuan Fu
2021-09-04 16:19 ` Eli Zaretskii
2021-09-06 3:07 ` Richard Stallman
2021-09-06 11:28 ` Dmitry Gutov
2021-09-04 19:55 ` Keybinding styles Daniel Fleischer
2021-09-04 20:52 ` Stefan Kangas
2021-09-05 7:17 ` tomas
2021-09-04 16:09 ` Bird
2021-09-04 20:48 ` Keybinding styles (was: [External] : Re: Gitlab Migration) Tim Cross
2021-09-05 19:03 ` John Yates
2021-09-06 4:34 ` Eli Zaretskii
2021-09-07 3:16 ` Richard Stallman
2021-09-07 12:02 ` John Yates
2021-09-08 3:29 ` Richard Stallman
2021-09-08 12:15 ` Keybinding styles André A. Gomes
2021-09-08 13:18 ` Eli Zaretskii
2021-09-08 20:37 ` John Yates
2021-09-09 5:39 ` Eli Zaretskii
2021-09-15 13:40 ` André A. Gomes
2021-09-15 14:26 ` Stefan Kangas
2021-09-15 15:36 ` Eli Zaretskii
2021-09-15 20:15 ` Richard Stallman
2021-09-15 21:29 ` Alexandre Garreau
2021-09-16 5:20 ` Eli Zaretskii
2021-09-16 5:00 ` Eli Zaretskii
2021-09-09 3:09 ` Richard Stallman
2021-09-04 16:05 ` [External] : Re: Gitlab Migration Stefan Kangas
2021-09-04 2:20 ` Drew Adams
2021-09-04 13:14 ` Stefan Monnier
2021-09-04 14:58 ` Drew Adams
2021-09-04 16:10 ` Stefan Monnier
2021-09-04 16:40 ` Drew Adams
2021-09-05 19:27 ` John Yates
2021-09-07 3:16 ` Richard Stallman
2021-09-07 15:31 ` Barry Fishman
2021-09-09 3:07 ` Richard Stallman
2021-09-09 14:07 ` André A. Gomes
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=831r64wda9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=theophilusx@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 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).