From: <tomas@tuxteam.de>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>,
Shahab Shahsavari Alavidjeh <zzgraph@gmail.com>
Subject: Re: Using AltGr as standard modifier key in emacs
Date: Wed, 14 Oct 2015 11:54:14 +0200 [thread overview]
Message-ID: <20151014095414.GD16469@tuxteam.de> (raw)
In-Reply-To: <CAP_d_8W=A4L_ru-snz9RfvpsdsWZr=gLA0b8_RNPH33EjdAJMQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, Oct 14, 2015 at 12:05:18PM +0600, Yuri Khan wrote:
[...]
Thanks for your lucid exposition of the problem.
> In light of (2), it is desirable that (a) the layouts in Emacs and the
> desktop environment are identical, (b) the keys to switch layouts are
> identical, and (c) the scope of layout switching is consistent. All
> three conditions are easiest satisfied by exclusively using the
> desktop-provided keyboard layout mechanism and ignoring Emacs input
> methods completely [...]
> desktop’s layouts using Emacs input methods, but I believe that is a
> dead end approach. There should be one, and preferably only one,
> implementation of keyboard layout mechanism over the whole desktop.)
>
> However, this comes at a cost. Because of the way modifiers work in
> Emacs when running as a GUI application, the user has no way of
> pressing e.g. C-c or C-x or M-x when a non-Latin layout is active.
> Instead, Emacs interprets the keypresses as being C- or M-modified
> letters of the active layout.
There are other costs -- among them that Emacs' input methods are usually
more advanced (and better integrated in Emacs) that whatever the desktop
can offer.
regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlYeJkYACgkQBcgs9XrR2kZ/KQCcDO0x28sKujYfhoDEzGgFtLOt
YB4AmwSHs2Vc8SOlBK18H23F0FUVt3OY
=PCU8
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-10-14 9:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 13:11 Using AltGr as standard modifier key in emacs Shahab Shahsavari Alavidjeh
2015-10-14 6:05 ` Yuri Khan
2015-10-14 6:47 ` Shahab Shahsavari Alavidjeh
2015-10-14 9:54 ` tomas [this message]
[not found] ` <mailman.289.1444802784.7904.help-gnu-emacs@gnu.org>
2015-10-14 12:17 ` Rusi
2015-10-15 1:47 ` Rusi
2015-10-15 2:23 ` Yuri Khan
[not found] ` <mailman.347.1444875907.7904.help-gnu-emacs@gnu.org>
2015-10-15 2:42 ` Rusi
[not found] <mailman.229.1444746928.7904.help-gnu-emacs@gnu.org>
2015-10-13 16:57 ` Rusi
2015-10-13 17:05 ` Rusi
2015-10-13 17:44 ` Shahab Shahsavari Alavidjeh
[not found] ` <mailman.256.1444758367.7904.help-gnu-emacs@gnu.org>
2015-10-13 18:19 ` Javier
2015-10-13 18:43 ` Javier
2015-10-13 19:42 ` Shahab Shahsavari Alavidjeh
[not found] ` <mailman.265.1444765466.7904.help-gnu-emacs@gnu.org>
2015-10-13 20:17 ` Javier
2015-10-14 5:18 ` Shahab Shahsavari Alavidjeh
2015-10-13 19:20 ` Shahab Shahsavari Alavidjeh
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=20151014095414.GD16469@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@gnu.org \
--cc=yuri.v.khan@gmail.com \
--cc=zzgraph@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.
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).