public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jorge Nerin <comandante@zaralinux.com>
To: Guest section DW <dwguest@win.tue.nl>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Win keys not working in console (2.4.x)
Date: Wed, 28 Mar 2001 01:33:41 +0200	[thread overview]
Message-ID: <3AC12355.6070207@zaralinux.com> (raw)
In-Reply-To: <3AC1072E.4080005@zaralinux.com> <20010328011148.A8265@win.tue.nl>

Guest section DW wrote:

> On Tue, Mar 27, 2001 at 11:33:34PM +0200, Jorge Nerin wrote:
> 
> 
>> Hello, good work with 2.4.x, but I miss one thing. in early 2.3.x the MS 
>> keys, you know, two flags and one "properties" key worked as navigation 
>> keys in the console.
>> 
>> The flags get you to the "left" or "rigth" virtual console, and the 
>> "properties" key put you on the last console you where before.
>> 
>> This was very useful when working in the console, I use the console 
>> sometimes, and I miss these feature.
> 
> 
> (i) Find out what key codes these keys generate.
> Vaguely I seem to recall that I made these keys produce 125, 126, 127.
> (the test command is "showkey")
> 
> (ii) Use loadkeys to assign functions to keys.
> For example,
> % loadkeys
> keycode 125 = Incr_Console
> keycode 126 = Decr_Console
> keycode 127 = Last_Console
> ^D
> should give you the desired behaviour.
> Perhaps you lost some settings during an upgrade.
> 
> See loadkeys(1) and keytables(5).

Oh, thanks, as you say I should have lost it in an upgrade, don't know 
how. I thougth it was a kernel issue, sorry. :(

Thanks.

-- 
Jorge Nerin
<comandante@zaralinux.com>


      reply	other threads:[~2001-03-27 23:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-27 21:33 Win keys not working in console (2.4.x) Jorge Nerin
2001-03-27 23:11 ` Guest section DW
2001-03-27 23:33   ` Jorge Nerin [this message]

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=3AC12355.6070207@zaralinux.com \
    --to=comandante@zaralinux.com \
    --cc=dwguest@win.tue.nl \
    --cc=linux-kernel@vger.kernel.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