All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clarence Dang <clarencedang@yahoo.com>
To: Paolo Gaggini <paolo@gseserver.net>
Cc: linux-msdos@vger.kernel.org
Subject: Re: CTRL+Fn and ALT+Fn mappings
Date: Wed, 3 Oct 2007 08:43:55 +1000	[thread overview]
Message-ID: <200710030843.58095.clarencedang@yahoo.com> (raw)
In-Reply-To: <4702742C.7060201@gseserver.net>

My wild guess is that your Window Manager (e.g. KDE) is trapping those keys. 
But I may be wrong.

On Wednesday 03 October 2007 2:39 am, Paolo Gaggini wrote:
> Hi all,
> here is a problem I've already seen discussed in the list, but with no
> clear answers for me.
>
> This is the context:
> - debian 4.0
> - dosemu 1.4.0
> - an old clipper application for dos, which uses CTRL+Fn and ALT+Fn
> combination keys to work
>
> I launch dosemu fron the console, the application works fine except for
> that key combination. If I press CTRL^cF1 it works as CTRL+F1, but this
> is a problem for me to use that unusual key combination.
>
> My keyboard is set as XLATE (ASCII 8bit) and with the linux command
> "showkey" I can see 4byte combination, for example the CONTROL+F1
> combination give me this 4 hex bytes: 0x1D 0x3B 0xBB 0x9D
> How can I modify kbd_slang.c to match this keycodes??
> Otherwise, there is a simple way to remapping CTRL+Fn/ALT+Fn ???
>
> Thank you in advance
> Paolo
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2007-10-02 22:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-02 16:39 CTRL+Fn and ALT+Fn mappings Paolo Gaggini
2007-10-02 22:43 ` Clarence Dang [this message]
2007-10-03  6:55   ` Paolo Gaggini
2007-10-03  7:03     ` Bart Oldeman
2007-10-03 11:35       ` Paolo Gaggini
2007-10-03 14:03         ` [solved] " Paolo Gaggini

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=200710030843.58095.clarencedang@yahoo.com \
    --to=clarencedang@yahoo.com \
    --cc=linux-msdos@vger.kernel.org \
    --cc=paolo@gseserver.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.