From: Richard Wordingham <richard.wordingham@ntlworld.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Switching non-English keyboard layouts and using Emacs shortcuts
Date: Wed, 13 May 2015 20:49:31 +0100 [thread overview]
Message-ID: <20150513204931.2748bab4@JRWUBU2> (raw)
In-Reply-To: <21842.65330.30641.47875@mail.eng.it>
On Wed, 13 May 2015 09:37:22 +0200
"Gian Uberto Lauri" <saint@eng.it> wrote:
> 2) use custom layout with a special sequence that changes the layout
> on the fly without using the setxkbmap command explicitly. I should
> ask my wife how to do this - she did it when she studied Arabic and
> Turkish;
In many X implementations one can combine up to 4 keyboards and choose
commands to cycle through them. I still find it awkward to bracket
each Emacs command or shortcut by cycling commands.
> 3) use an Emacs input method (tamil-inscript or tamil-itrans)
> I think that 2) is a bit 'heaveier' than 3) as for Emacs commands, but
> 2) is much better than 3) for entering a long text.
How is (2) better than (3) for long text? Are you saying the input
methods are too slow? I don't see any such problem for methods with one
(modified) keystroke = one input character, which is the X paradigm.
(X does exhort programs to support a specific set of dead keys.)
Richard.
next prev parent reply other threads:[~2015-05-13 19:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 4:35 Switching non-English keyboard layouts and using Emacs shortcuts Shakthi Kannan
2015-05-13 5:24 ` Richard Wordingham
2015-05-20 9:38 ` Shakthi Kannan
2015-10-08 17:49 ` Shakthi Kannan
2015-10-18 19:50 ` Thien-Thi Nguyen
2015-10-20 17:58 ` Shakthi Kannan
2015-10-22 19:40 ` Thien-Thi Nguyen
2015-10-23 4:44 ` Shakthi Kannan
2015-05-13 7:37 ` Gian Uberto Lauri
2015-05-13 19:49 ` Richard Wordingham [this message]
2015-05-20 9:41 ` Shakthi Kannan
2015-05-13 9:02 ` Yuri Khan
2015-05-20 9:43 ` Shakthi Kannan
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=20150513204931.2748bab4@JRWUBU2 \
--to=richard.wordingham@ntlworld.com \
--cc=help-gnu-emacs@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.
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).