unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Using AltGr as standard modifier key in emacs
Date: Wed, 14 Oct 2015 18:47:53 -0700 (PDT)	[thread overview]
Message-ID: <a7541cfa-69c2-451e-85a0-dd23399d8d97@googlegroups.com> (raw)
In-Reply-To: <113e5ac1-2eea-4d88-ad2e-7864e79a6cc6@googlegroups.com>

On Wednesday, October 14, 2015 at 5:47:26 PM UTC+5:30, Rusi wrote:
> On Wednesday, October 14, 2015 at 11:36:26 AM UTC+5:30, Yuri Khan wrote:
> > 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.
> 
> I find this behavior at least anomalous, maybe a bug.
> 
> $ setxkbmap -layout "us,gr" -option "grp:lalt_lshift_toggle,grp_led:scroll"
> 
> gets a greek keyboard after lshift-lalt
> 
> Now inside emacs the normal keys produce greek thus:
> abcdefghijkl produces αβψδεφγηιξκλ
> 
> So far so good
> 
> C-a produces a 
> C-α is undefined
> message
> 
> However M-x (ie Alt-x) works alright
> 
> So why does C- go through the current layout
> Whereas M- stays within us/Ascii?

And with emacs -nw
its the other way round: M-x doesnt work, C-x does


  reply	other threads:[~2015-10-15  1:47 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
     [not found] ` <mailman.289.1444802784.7904.help-gnu-emacs@gnu.org>
2015-10-14 12:17   ` Rusi
2015-10-15  1:47     ` Rusi [this message]
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=a7541cfa-69c2-451e-85a0-dd23399d8d97@googlegroups.com \
    --to=rustompmody@gmail.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).