From: Thomas LIMIN <thomas.limin@gmail.com>
To: cygwin@cygwin.com
Subject: Altgr+space doesn't print the expected character when using bash and bépo keyboard layout
Date: Wed, 23 Feb 2011 17:58:00 -0000 [thread overview]
Message-ID: <AANLkTinFWQhA4rAJtYTr-NvC2pOgAgscGEsgq0S+m6CG@mail.gmail.com> (raw)
Hello
I'm using Cygwin on Windows Seven 64bit, with the bépo keyboard layout
(http://bepo.fr/wiki/Accueil bépo is a keyboard layout optimized for
french users)
Using this layout, I can't write a '_' in bash.
bépo layout binds '_' to the key sequence Ctrl+Alt+SPACE (or Altgr+SPACE).
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 = 00)
With vi, in insertion mode, pressing Ctrl+Alt+SPACE (or Altgr+SPACE)
trigger this message: E29: No inserted text yet
However, other bépo 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
next reply other threads:[~2011-02-23 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 17:58 Thomas LIMIN [this message]
2011-06-24 7:02 ` menfin
2011-06-24 8:34 ` Corinna Vinschen
2011-06-24 8:56 ` menfin
2011-06-24 9:20 ` Andy Koppe
2011-06-24 12:13 ` menfin
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=AANLkTinFWQhA4rAJtYTr-NvC2pOgAgscGEsgq0S+m6CG@mail.gmail.com \
--to=thomas.limin@gmail.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).