From: Alexey Dobriyan <adobriyan@gmail.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
hpa@zytor.com, alan@lxorguk.ukuu.org.uk, mgarski@post.pl
Subject: Re: [PATCH] kbd: (#7063) make CapsLock work as expected even for non-ASCII
Date: Mon, 16 Nov 2009 22:53:13 +0300 [thread overview]
Message-ID: <20091116195313.GB4462@x200> (raw)
In-Reply-To: <20091116190739.GJ4764@const.famille.thibault.fr>
On Mon, Nov 16, 2009 at 08:07:39PM +0100, Samuel Thibault wrote:
> Alexey Dobriyan, le Mon 16 Nov 2009 16:51:15 +0300, a écrit :
> > Steps to reproduce:
> >
> > [log into console (not xterm)]
> > [load non-trivial keymap]
> > [turn on CapsLock]
> > [type something]
> >
> > Symbols won't be capital despite CapsLock and despite Shift+* working
> > as expected.
>
> Fix your keymap, it should use KT_LETTER instead of KT_LATIN.
You have read bugzilla and patch, haven't you?
My keymap contains
keycode 44 = +z
shift keycode 44 = +Z
altgr keycode 44 = U+044F # CYRILLIC SMALL LETTER YA
altgr shift keycode 44 = U+042F # CYRILLIC CAPITAL LETTER YA
> > Note: patch relies on keymap being consistent wrt SMALL/CAPITAL symbols.
>
> And that's not true for a lot of keyboard symbols.
That's why patch implies keymap is not fucked up.
> Strictly speaking, caps lock is caps lock, not shift lock. If you really
> want a shift lock, then set your caps lock key to produce shift lock.
> Applying your patch would turn the existing capslock behavior into shift
> lock, we _don't_ want that.
>
> > Though extracting SMALL <=> CAPITAL mapping from unicode tables and
> > putting it into kernel may be more correct.
>
> That's what console-setup
What is it?
$ sudo emerge -s console-setup
Searching...
[ Results for search key : console-setup ]
[ Applications found : 0 ]
> does by using various symbol levels and it just _works_.
Ubuntu user?
> One issue however is that then the capslock keyboard
> led doesn't light up while in caps mode.
Interesting breakage you have.
[presses CapsLock several times]
> Maybe we should rethink the interface to light keyboard leds instead.
Oh, and there no need to reply at every place as if Linus is going to
grab it from bugzilla and apply in hurry.
next prev parent reply other threads:[~2009-11-16 19:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 13:51 [PATCH] kbd: (#7063) make CapsLock work as expected even for non-ASCII Alexey Dobriyan
2009-11-16 14:40 ` Alan Cox
2009-11-16 19:08 ` Samuel Thibault
2009-11-16 19:07 ` Samuel Thibault
2009-11-16 19:53 ` Alexey Dobriyan [this message]
2009-11-16 22:27 ` Samuel Thibault
2009-11-16 22:53 ` Alexey Dobriyan
2009-11-16 23:04 ` Samuel Thibault
2009-11-16 22:54 ` Samuel Thibault
2009-11-16 23:05 ` Alexey Dobriyan
2009-11-16 23:15 ` Samuel Thibault
2009-11-17 11:55 ` Alexey Dobriyan
2009-11-17 13:23 ` Samuel Thibault
2009-11-19 13:18 ` Alexey Dobriyan
2009-11-19 13:28 ` Samuel Thibault
2009-11-19 13:37 ` Samuel Thibault
2009-11-19 15:07 ` H. Peter Anvin
2009-11-20 19:07 ` Pavel Machek
2009-11-20 20:46 ` Pavel Machek
2009-11-20 21:27 ` H. Peter Anvin
2010-02-21 5:01 ` [RFC,PATCH] Route kbd leds through the generic leds layer (Was: [PATCH] kbd: (#7063) make CapsLock work as expected even for non-ASCII) Samuel Thibault
2010-02-23 16:30 ` Pavel Machek
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=20091116195313.GB4462@x200 \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgarski@post.pl \
--cc=samuel.thibault@ens-lyon.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