From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: tomas@tuxteam.de
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>,
Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Subject: Re: Consult some suggestions for adjusting keyboard shortcuts to bind conflicts.
Date: Mon, 12 Apr 2021 17:06:22 +0800 [thread overview]
Message-ID: <CAGP6PO+Pvy=yuLneSxuES5eQ-9V1CktMMxbw-C3_1b9cy_Kvfg@mail.gmail.com> (raw)
In-Reply-To: <20210412075911.GC17156@tuxteam.de>
On Mon, Apr 12, 2021 at 3:59 PM <tomas@tuxteam.de> wrote:
>
> On Mon, Apr 12, 2021 at 02:19:07PM +0800, Hongyi Zhao wrote:
> > On Mon, Apr 12, 2021 at 4:16 AM Nikolay Kudryavtsev
> > <nikolay.kudryavtsev@gmail.com> wrote:
> > >
> > > Well, do you use M-s prefix commands? I seldom do, so I've rebound them
> > > to another prefix and use M-s for window switching instead.
> > >
> > > As for running Emacs with multiple input systems, my usual setup is
> > > setting up the OS to switch input language on Caps Lock and Ctrl+Shift,
> > > since neither of those keys mess with Emacs in any way and I seldom need
> > > Caps Lock.
> >
> > Caps Lock in itself will (de)activate the capital character input
> > mode, so, I think maybe Ctrl+Shift is more preferable.
>
> I'm another of those re-using Caps Lock for something different. In
> my case, I use double-shift (i.e. left-shift + right-shift) to switch
> language, and caps lock for Compose (I ♥ compose: very handy :)
What do you mean by saying "compose"?
> See, I'm an old guy: my fingers were trained on a mechanical typewriter,
> and there caps-lock kind of made sense; since "shift" had to push the
> whole type cluster around, it was hard to keep shift pushed with the
> pinky while typing a couple of letters.
>
> Since computer keyboards, I realised that I had no use for caps lock
> (except for pushing it accidentaly while entering passwords, that
> is ;-)
>
> Cheers
> - t
--
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Polytechnic University of Science and Technology engineering
NO. 552 North Gangtie Road, Xingtai, China
next prev parent reply other threads:[~2021-04-12 9:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 1:39 Consult some suggestions for adjusting keyboard shortcuts to bind conflicts Hongyi Zhao
2021-04-08 7:06 ` Robert Thorpe
2021-04-10 13:40 ` Hongyi Zhao
2021-04-11 20:16 ` Nikolay Kudryavtsev
2021-04-12 6:19 ` Hongyi Zhao
2021-04-12 7:59 ` tomas
2021-04-12 9:06 ` Hongyi Zhao [this message]
2021-04-12 9:22 ` tomas
2021-04-13 22:23 ` Robert Thorpe
2021-04-14 0:31 ` Hongyi Zhao
2021-04-10 14:26 ` Gregory Heytings
2021-04-11 0:22 ` Hongyi Zhao
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='CAGP6PO+Pvy=yuLneSxuES5eQ-9V1CktMMxbw-C3_1b9cy_Kvfg@mail.gmail.com' \
--to=hongyi.zhao@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=nikolay.kudryavtsev@gmail.com \
--cc=tomas@tuxteam.de \
/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.
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).