CTRL+Fn and ALT+Fn mappings
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
My wild guess is that your Window Manager (e.g. KDE) is trapping those keys. But I may be wrong.
Quoted 27 lines · Paolo Gaggini
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 workI 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:
0x1D0x3B0xBB0x9DHow can I modifykbd_slang.cto 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Thank you for the answer, but:
1) the problem affects only the linux console (without X I mean)
2) using X (xorg) it seems works, in this ways:
A) X + Fluxbox: CTRL+Fn works, ALT+Fn switch virtual desktops; no fullscreen
B) X + Blackbox: all keys work; no fullscreen
C) X alone, without any window manager but with xterm attached: keys work and fullscreen too.
The problem with the X-solution is that the fonts are ugly (I'm trying to solve this) and ofcourse I need install the X server with all libraries etc.
My goal is instead to get working a small linux dosbox that can fit in a small space (512MB/1GB) and can full run a legacy clipper application, so for this I should need CTRL+Fn/ALT+Fn combination in native linux console without X.
In the mailing list archive, I've found someone suggesting in the past the modification of src/plugin/term/kbd_slang.c file in order to remapping that combinations but I can't understand how to do it...
Clarence Dang ha scritto:
Quoted 30 lines
My wild guess is that your Window Manager (e.g. KDE) is trapping those keys. But I may be wrong.
Quoted 27 lines · Paolo Gaggini
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 workI 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:
0x1D0x3B0xBB0x9DHow can I modifykbd_slang.cto 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 3 lines · Paolo Gaggini
Thank you for the answer, but:
1) the problem affects only the linux console (without X I mean)
In that case you should be able to use the raw keyboard ($_rawkeyboard = (1) or the -k switch).
Unless DOSEMU is run remotely (or even from inside mc), in which case there is a lot more to configure.
Bart
Already tried, but with no success.
I run dosemu not remotely but just in front of the PC using its attached keyboard.
The TERM env var is set to "linux" and the keyboard mode is XLATE (ASCII). I've an old PC with redhat9 (not configured by me and I don't know who done) in which the CTRL/ALT combinations works fine; in this PC I can see that the TERM var is "xterm" (even if I don't use X neither on this pc) and the keyboard mode is RAW. In its dosemu.conf $_rawkeyboard
is effectively set to 1.
Any idea about this differences?
However, there is somewhere some written docs about the "lot more to configure"?
Thank you anyway
Paolo
Bart Oldeman ha scritto:
Quoted 16 lines · Paolo Gaggini
Quoted 3 lines
Thank you for the answer, but:
1) the problem affects only the linux console (without X I mean)
In that case you should be able to use the raw keyboard ($_rawkeyboard = (1) or the -k switch).
Unless DOSEMU is run remotely (or even from inside mc), in which case there is a lot more to configure.
Bart
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Solved, excuse me it was a my failure... I misunderstood the comment in the dosemu.conf about the $_rawkeyboard, I assumed that "auto" means "1" (so I kept auto and not set directly 1)..... sorry to have disturbed you for this!
Thank you
Bye
Paolo Gaggini ha scritto:
Quoted 34 lines
Already tried, but with no success.
I run dosemu not remotely but just in front of the PC using its attached keyboard.
The TERM env var is set to "linux" and the keyboard mode is XLATE (ASCII). I've an old PC with redhat9 (not configured by me and I don't know who done) in which the CTRL/ALT combinations works fine; in this PC I can see that the TERM var is "xterm" (even if I don't use X neither on this pc) and the keyboard mode is RAW. In its dosemu.conf $_rawkeyboard
is effectively set to 1.
Any idea about this differences?However, there is somewhere some written docs about the "lot more to configure"?
Thank you anyway
PaoloBart Oldeman ha scritto:
Quoted 8 lines · Paolo Gaggini
Quoted 3 lines
Thank you for the answer, but:
1) the problem affects only the linux console (without X I mean)
In that case you should be able to use the raw keyboard ($_rawkeyboard = (1) or the -k switch).
Quoted 8 lines
Unless DOSEMU is run remotely (or even from inside mc), in which case there is a lot more to configure.
Bart
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html