public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Issue with inserting '@' at the command prompt.
Date: Fri, 19 Aug 2011 15:33:00 -0000	[thread overview]
Message-ID: <20110819153227.GA21235@calimero.vinschen.de> (raw)
In-Reply-To: <20110819151545.GA4919@type.famille.thibault.fr>

On Aug 19 17:15, Samuel Thibault wrote:
> Corinna Vinschen, le Fri 19 Aug 2011 17:08:41 +0200, a écrit :
> > Yes, just like the german one.  However, to the best of my knowledge
> > there's no printable unicode char which requires to press left-alt on
> > any such keyboard layout.
> 
> Yes, but there are shortcuts which use left-alt.
> 
> > That's exactly what the AltGr == right-alt key is for, isn't it?
> 
> For glyphs, yes.
> 
> For instance, alt-e would open an edition menu, while altgr-e prints the
> euro symbol.

Sure, but for the shortcuts, the keyboard doesn't generate a valid
unicode.  I think we're in violent agreement, just using different
expressions for it.

> > Uh, ok, I see.  If you press AltGr on a keyboard layout which does not
> > distinguish Alt and AltGr, (english, for instance), the AltGr key only
> > emits a RIGHT_ALT_PRESSED control code.
> 
> Ok.
> 
> > On a keyboard layout which does
> > distinguish them, the AltGr key emits LEFT_CTRL_PRESSED | RIGHT_ALT_PRESSED.
> 
> Ah. *that* is the part that I was missing :) I had assumed that
> RIGHT_ALT meant altgr. So we'll indeed simply simulate control as well,
> and it should work correctly.
> 
> Thanks!

Glad I could help,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2011-08-19 15:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 11:42 [Lars Bjørndal] Re: brltty problems with recent snapshots Lars Bjørndal
2011-07-13 12:35 ` Lars Bjørndal
2011-07-13 13:07   ` Corinna Vinschen
2011-07-13 15:37   ` Christopher Faylor
2011-07-13 13:06 ` [Lars Bjørndal] " Corinna Vinschen
2011-07-13 13:37   ` Samuel Thibault
2011-07-13 19:01     ` Corinna Vinschen
2011-07-13 19:25       ` Lars Bjørndal
2011-07-13 20:00         ` Corinna Vinschen
2011-07-14  8:20       ` Lars Bjørndal
2011-07-14 10:16         ` Corinna Vinschen
2011-07-14 10:56           ` Lars Bjørndal
2011-07-14 12:42             ` Samuel Thibault
2011-08-19  2:38               ` Issue with inserting '@' at the command prompt Samuel Thibault
2011-08-19  2:45                 ` Samuel Thibault
2011-08-19 11:50                 ` Corinna Vinschen
2011-08-19 13:15                   ` Samuel Thibault
2011-08-19 13:51                     ` Corinna Vinschen
2011-08-19 14:07                     ` Samuel Thibault
2011-08-19 15:09                       ` Corinna Vinschen
2011-08-19 15:16                         ` Samuel Thibault
2011-08-19 15:33                           ` Corinna Vinschen [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110819153227.GA21235@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.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).