MIME-Version: 1.0
Date: Wed, 23 Feb 2011 18:56:37 +0100
Message-ID: <AANLkTinFWQhA4rAJtYTr-NvC2pOgAgscGEsgq0S+m6CG@mail.gmail.com>
Subject: =?UTF-8?Q?Altgr=2Bspace_doesn=27t_print_the_expected_character_whe?=	=?UTF-8?Q?n_using_bash_and_b=C3=A9po_keyboard_layout?=
From: Thomas LIMIN <thomas.limin@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Hello

I'm using Cygwin on Windows Seven 64bit, with the b=C3=A9po keyboard layout
(http://bepo.fr/wiki/Accueil  b=C3=A9po is a keyboard layout optimized for
french users)

Using this layout, I can't write a '_' in bash.

b=C3=A9po layout binds  '_' to the key sequence Ctrl+Alt+SPACE (or Altgr+SP=
ACE).

All native windows applications understand this sequence, and print a '_'.

However, pressing Ctrl+Alt+SPACE (or Altgr+SPACE) when I'm at the bash
prompt doesn't print anything.

If I write directly to cat standard input (after typing 'cat' and
press return), then I get what looks like a space, but is a null
character (hexadecimal ascii code =3D 00)

With vi, in insertion mode, pressing Ctrl+Alt+SPACE (or Altgr+SPACE)
trigger this message: E29: No inserted text yet


However, other b=C3=A9po bindings, including Altgr bindings,  works
seemlessly, and I can get all the characters, even no ascii and
accentuated characters.

It seems that the only key sequence encountering issue is
Ctrl+Alt+SPACE (or Altgr+SPACE).

Does cygwin or one of the underlying library handles this sequence in
a specific way?

Does someone has already encountered an issue with altgr+space binding
and know how to resolve it?


Best regards

Thomas LIMIN

--
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