From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: dosemu-1.1.3 and Cyrillic_er
Date: Wed, 24 Apr 2002 17:02:01 +0400 [thread overview]
Message-ID: <3CC6ACC9.8040808@yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
Hello.
Sergey Suleymanov wrote:
>>> Any ideas why this happens with BackSpace?
> Stas> Well, turning off X_keycode "fixes" the problem. Can live with
> Stas> this:)
> Hmm, can't reproduce that :(. 3592 in both modes.
Well, I have investigated a little more
and found that the attached patch fixes
the problem. Actually only the change to
altgr table is enough.
Does this help?
Why 127 is there?
[-- Attachment #2: keymaps.diff --]
[-- Type: text/plain, Size: 1456 bytes --]
--- src/plugin/kbd_unicode/keymaps.c Tue Apr 23 17:32:37 2002
+++ src/plugin/kbd_unicode/keymaps.c Wed Apr 24 16:53:09 2002
@@ -1755,7 +1755,7 @@
CONST t_keysym key_map_ru[] =
{
U_VOID, 27, '1', '2', '3', '4', '5', '6',
- '7', '8', '9', '0', '-', '=', 127, 9,
+ '7', '8', '9', '0', '-', '=', 8, 9,
'q', 'w', 'e', 'r', 't', 'y', 'u', 'i',
'o', 'p', '[', ']', 13, U_VOID, 'a', 's',
'd', 'f', 'g', 'h', 'j', 'k', 'l', ';',
@@ -1772,7 +1772,7 @@
CONST t_keysym shift_map_ru[] =
{
U_VOID, 27, '!', '@', '#', '$', '%', '^',
- '&', '*', '(', ')', '_', '+', 127, 9,
+ '&', '*', '(', ')', '_', '+', 8, 9,
'Q', 'W', 'E', 'R', 'T', 'Y', 'U', 'I',
'O', 'P', '{', '}', 13, U_VOID, 'A', 'S',
'D', 'F', 'G', 'H', 'J', 'K', 'L', ':',
@@ -1789,7 +1789,7 @@
CONST t_keysym altgr_map_ru[] =
{
U_VOID, 27, '1', '2', '3', '4', '5', '6',
- '7', '8', '9', '0', '-', '=', 127, 9,
+ '7', '8', '9', '0', '-', '=', 8, 9,
0x439,0x446,0x443,0x43A,0x435,0x43D,0x433,0x448,0x449,0x437,0x445,0x44A,
13, U_VOID,
0x444,0x44B,0x432,0x430,0x43F,0x440,0x43E,0x43B,0x434,0x436,0x44D,0x451,
@@ -1807,7 +1807,7 @@
CONST t_keysym shift_altgr_map_ru[] =
{
U_VOID, 27, '!', '@', '#', '$', '%', '^',
- '&', '*', '(', ')', '_', '+', 127, 9,
+ '&', '*', '(', ')', '_', '+', 8, 9,
0x419,0x426,0x423,0x41A,0x415,0x41D,0x413,0x428,0x429,0x417,0x425,0x42A,
13, U_VOID,
0x424,0x42B,0x412,0x410,0x41F,0x420,0x41E,0x41B,0x414,0x416,0x42D,0x401,
next reply other threads:[~2002-04-24 13:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 13:02 Stas Sergeev [this message]
2002-04-24 14:15 ` dosemu-1.1.3 and Cyrillic_er Sergey Suleymanov
-- strict thread matches above, loose matches on Subject: below --
2002-04-25 19:29 Stas Sergeev
2002-04-25 21:05 ` Grigory Batalov
2002-04-25 14:23 Stas Sergeev
2002-04-26 11:18 ` Sergey Suleymanov
2002-04-24 13:13 Stas Sergeev
2002-04-24 13:13 Stas Sergeev
2002-04-24 14:05 ` Grigory Batalov
2002-04-24 14:39 ` Sergey Suleymanov
2002-04-24 19:08 ` Grigory Batalov
2002-04-23 17:15 Stas Sergeev
2002-04-24 6:10 ` Sergey Suleymanov
2002-04-24 6:38 ` Grigory Batalov
2002-04-24 9:18 ` Sergey Suleymanov
2002-04-23 15:00 Stas Sergeev
2002-04-23 11:06 Stas Sergeev
2002-04-23 11:29 ` Sergey Suleymanov
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=3CC6ACC9.8040808@yahoo.com \
--to=stssppnn@yahoo.com \
--cc=linux-msdos@vger.kernel.org \
--cc=stas.orel@mailcity.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