From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: 113: plugin/keyboard vs. plugin/kbd_unicode ?
Date: Tue, 30 Jul 2002 00:21:00 +0400 [thread overview]
Message-ID: <3D45A3AC.4030009@yahoo.com> (raw)
Hello.
Per Jessen wrote:
> In plugin/kbd_unicode, "no keyboard" is explicitly recognised,
> but doesn't seem to default to reading stdin ?
Looking in keyb_none.c it seems
that "no keyboard" does absolutely
nothing - just a dummy client.
Raw keyboard client seems to be
using stdin (see raw_keyboard_init() ).
> Which part of the keyboard code is actually being used for 113 ?
non-unicode one.
> Eric Biedermans kbd_unicode looks somewhat cleaner, but it is
> not the default that is "shipped"?
It is default since 1.1.3.2 so
upgrade if you are going to do
some hacking.
As of your other message: lredir
still works OK for me (1.1.3.2)
next reply other threads:[~2002-07-29 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 20:21 Stas Sergeev [this message]
2002-07-29 21:34 ` 113: plugin/keyboard vs. plugin/kbd_unicode ? Bart Oldeman
2002-07-30 9:54 ` Per Jessen
2002-07-30 9:49 ` Per Jessen
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=3D45A3AC.4030009@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