Do keymaps need to be in /usr/...?
Hello, disk decryption works for me when I put kbdcontrol -l /usr/share/syscons/keymaps/german.iso.kbd into /etc/rc.d/geli. But do the keymaps need to be in a file system which may be mounted delayed? If there is an error at boot time and something needs to be input to the console the keyboard can be considered as unusable until the correct keymap has been set. Carsten ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Keymaps in X11 and consoles should be the same with TEKEN_XTERM in the kernel.
TEKEN_XTERM turns on xterm mode. I compiled a kernel with TEKEN_XTERM, and changed cons25 to xterm in /etc/ttys. When I executed vim on a console, the keyboard acted weirdly. After setting TERM back to cons25 again, vim acted normally again on consoles. I could assign xterm console characters in /etc/termcap to fkeys by writing keychanges=fkeycode consolecharacter in /etc/rc.conf, but it is just a quick hack, and it is just a solution for me but not for everyone. I would be glad keymaps in X11 and consoles became the same with TEKEN_XTERM in the kernel. If the keymaps in consoles and X11 are the same, 99% of configurations I needed to make in applications will be unneeded. It will benefit everyone. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Keymaps in X11 and consoles should be the same with TEKEN_XTERM in the kernel.
On 13 November 2010 15:52, crocket crockabisc...@yahoo.com wrote: TEKEN_XTERM turns on xterm mode. I compiled a kernel with TEKEN_XTERM, and changed cons25 to xterm in /etc/ttys. When I executed vim on a console, the keyboard acted weirdly. After setting TERM back to cons25 again, vim acted normally again on consoles. I could assign xterm console characters in /etc/termcap to fkeys by writing keychanges=fkeycode consolecharacter in /etc/rc.conf, but it is just a quick hack, and it is just a solution for me but not for everyone. Oh... you can do `vidcontrol -T xterm` and your keybindings will be correct. I would be glad keymaps in X11 and consoles became the same with TEKEN_XTERM in the kernel. If the keymaps in consoles and X11 are the same, 99% of configurations I needed to make in applications will be unneeded. It will benefit everyone. As Ed said some days before, you should use TEKEN_XTERM _or_ TEKEN_CONS25 in your kernel. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Keymaps in X11 and consoles should be the same with TEKEN_XTERM in the kernel.
* crocket crockabisc...@yahoo.com, 20101113 13:52: TEKEN_XTERM turns on xterm mode. I compiled a kernel with TEKEN_XTERM, and changed cons25 to xterm in /etc/ttys. When I executed vim on a console, the keyboard acted weirdly. Keep in mind that this list is supposed to discuss FreeBSD -CURRENT; not FreeBSD 8.x. Please don't use xterm mode on FreeBSD 8. It doesn't come with any support whatsoever. -- Ed Schouten e...@80386.nl WWW: http://80386.nl/ pgp07pH8M2FcF.pgp Description: PGP signature
Re: Keymaps in X11 and consoles should be the same with TEKEN_XTERM in the kernel.
--- On Sat, 11/13/10, Eir Nym eir...@gmail.com wrote: From: Eir Nym eir...@gmail.com Subject: Re: Keymaps in X11 and consoles should be the same with TEKEN_XTERM in the kernel. To: crocket crockabisc...@yahoo.com Cc: freebsd-current@freebsd.org Date: Saturday, November 13, 2010, 4:54 PM On 13 November 2010 15:52, crocket crockabisc...@yahoo.com wrote: TEKEN_XTERM turns on xterm mode. I compiled a kernel with TEKEN_XTERM, and changed cons25 to xterm in /etc/ttys. When I executed vim on a console, the keyboard acted weirdly. After setting TERM back to cons25 again, vim acted normally again on consoles. I could assign xterm console characters in /etc/termcap to fkeys by writing keychanges=fkeycode consolecharacter in /etc/rc.conf, but it is just a quick hack, and it is just a solution for me but not for everyone. Oh... you can do `vidcontrol -T xterm` and your keybindings will be correct. When I execute 'vidcontrol -T xterm', vidcontrol: illegal option -- T is displayed. Ah, I use FreeBSD 8.1-RELEASE, not -CURRENT. Maybe that's why I don't have -T option. I posted my message here because development of TEKEN_XTERM is an ongoing process. I would be glad keymaps in X11 and consoles became the same with TEKEN_XTERM in the kernel. If the keymaps in consoles and X11 are the same, 99% of configurations I needed to make in applications will be unneeded. It will benefit everyone. As Ed said some days before, you should use TEKEN_XTERM _or_ TEKEN_CONS25 in your kernel. I don't understand what you answered to. However, TEKEN_CONS25 is not in my kernel configuration. And There was a typo. I would be glad keymaps in X11 and consoles became the same with TEKEN_XTERM in the kernel should be I would be glad if keymaps in X11 and consoles became the same with TEKEN_XTERM in the kernel Do you think xterm way(instead of syscons way) of key symbol to console character conversion should become the default in 9.0-RELEASE? I think it should be since syscons is being replaced by teken, which uses xterm. I'm not sure if I used terms right. PS. teken reminds me of tekken, an arcade game. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Keymaps in X11 and consoles should be the same with TEKEN_XTERM in the kernel.
Does Delete key match \E[3~ on FreeBSD-CURRENT xterm mode? It's nice to see backspace key match ^?(ASCII DEL), too, since ^H(Ctrl-H) is reserved by such applications as vim and emacs. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Keymaps in X11 and consoles should be the same with TEKEN_XTERM in the kernel.
On 13/11/2010, crocket crockabisc...@yahoo.com wrote: Does Delete key match \E[3~ on FreeBSD-CURRENT xterm mode? It's nice to see backspace key match ^?(ASCII DEL), too, since ^H(Ctrl-H) is reserved by such applications as vim and emacs. For witch action C-H is reserved in vim(1) ? vim, emacs, zsh, and many others use termcap(5) to determine which key generate which sequence. Please note, that xterm and xterm-colors termcap entries are differs, and last is not usable in FreeBSD-CURRENT TEKEN_XTERM console. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: keymaps
Kazutaka YOKOTA wrote: * Summary of magic key sequences 101 keyboard84 keyboard function Ctrl-Alt-Delete Ctrl-Alt-Delete reboot Ctrl-Alt-EscCtrl-Alt-Escdebug Ctrl-Alt-Space Ctrl-Alt-Space susp ScrollLock ScrollLock slock PrintScreen Shift-(Numpad *)/PrintScreennscr Ctrl-PrintScreenShift-Ctrl-(Numpad *)/PrintScreen debug Alt-PrintScreen/SysRq SysRq nop Pause Ctrl-NumLockslock Shift-Pause Shift-Ctrl-NumLock saver Alt-Pause Alt-Ctrl-NumLocksusp Ctrl-Pause/BreakCtrl-ScrollLock/Break nop Nihil obstat :-) -- JMA --- José Mª Alcaide | mailto:j...@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 --- Go ahead... make my day. - H. Callahan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: keymaps
On Jan 21, 9:40pm, Warner Losh wrote: } Subject: Re: keymaps } In message 199901220043.laa22...@lightning.itga.com.au Gregory Bond writes: } : my vote: A version of the standard keymap with CapsLock and LeftCtl } : functions swapped so the control key is under my left finger like } : God intended! } } What's wrong with us.unix.kbd? Two things for me: It's not in the sysinstall menu. I'm not sure I like the Esc - ~` swap. Does anyone know of any decent PC keyboards with a Unix-friendly layout? I'm pretty happy with the layout on a Sun Type-5 keyboard, which puts Esc right above Tab and to the left of 1 (where PC's generally have ~`). The Return key is wide, but is confined to the home row, and Backspace is also wide and is in the row immediately above it. This leaves room in the top row (below the function keys, where PC's put Backspace), for |\, which PC keyboards put in various random places, and ~`. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: keymaps
I recently looked at keymaps in /usr/share/syscons/keymaps and found many minor errors. In addition to that, there is so much inconsistency among existing keymaps. True that national keyboards have different layout of regular keys (alphanumeric keys and symbol keys). But, it is absurd that functions keys and special keys are handled in so many different ways. [...] But, unless there is a good reason to make other exceptions, I will modify the other national keymaps to adapt these key assignments. Any comments? I am open to suggestions. Kazu Ok, this is my second keymap proposal. Kazu * 101/102/104 Enhanced Keyboard support Key CodeKey Stroke Function - 1 Ctrl-Alt-EscEnter DDB (debug). 57 Ctrl-Alt-Space Suspend (susp). 70 ScrollLock Backscroll (slock). 84 Alt-SysRq(PrintScreen) - (nop) 92 PrintScreen Switch to the next vty (nscr). 92 Ctrl-PrintScreenEnter DDB (debug). 104 Pause Backscroll (slock). 104 Shift-Pause Start screen saver (saver). 104 Alt-Pause Suspend (susp). 105 Left Windowsfkey62 106 Right Windows fkey63 107 Menufkey64 108 Ctrl-Break(Pause) - (nop) The separate SysRq key doesn't exist on the enhanced keyboard. It is combined with the PrintScreen key. The SysRq code is generated when the Alt and the PrintScreen keys are pressed together. The separate Break key doesn't exist on the enhanced keyboard. It is combined with the Pause key. The Break code is generated when the Ctrl and the Pause keys are pressed together. The above assignments for the keycodes 1, 57, 70, 84 and 92 are compatible with many, if not all, existing keymaps. The base case for the keycode 104 is compatible with existing keymaps. The keycode 108 is new. Many keymaps lacks entries for 105 through 107. * 84 Keyboard support Key CodeKey Stroke Function - 1 Ctrl-Alt-EscEnter DDB (debug). 57 Ctrl-Alt-Space Suspend (susp). 70 ScrollLock Backscroll (slock). 84 SysRq - (nop) 92 Shift-PrintScreen(*)Switch to the next vty (nscr). 92 Shift-Ctrl-PrintScreen Enter DDB (debug). 104 Ctrl-Pause(NumLock) Backscroll (slock). 104 Shift-Ctrl-Alt-Pause(NumLock) Start screen saver (saver). 104 Ctrl-Alt-Pause(NumLock) Suspend (susp). 108 Ctrl-Break(ScrollLock) - (nop) The separate PrintScreen key doesn't exist on the 84 keyboard. It is combined with the numpad * key. The PrintScreen code is generated when the Shift and the numpad * keys are pressed together. The separate Pause key doesn't exist on the 84 keyboard. It is combined with the NumLock key. The Pause code is generated when the Ctrl and the NumlLock keys are pressed together. The separate Break key doesn't exist on the 84 keyboard. It is combined with the ScrollLock key. The Break code is generated when the Ctrl and the ScrollLock keys are pressed together. * Proposed keymap Combining the support for the 84 keyboard and the enhanced keyboard described above, we will get the following keymap entries. alt ctrlalt alt ctrl code base shift ctrl shift alt shift ctrl shift - 1 esc esc esc esc esc esc debug esc 57 ' ' ' ' null ' ' ' ' ' ' susp ' ' 70 slock slock slock slock slock slock slock slock 84 nop nop nop nop nop nop nop nop 92 nscr nscr debug debug nop nop nop nop 104 slock saver slock saver susp nop susp nop 105 fkey62fkey62fkey62fkey62fkey62fkey62fkey62fkey62 106 fkey63fkey63fkey63fkey63fkey63fkey63fkey63fkey63 107 fkey64fkey64fkey64fkey64fkey64fkey64fkey64fkey64 108 nop nop nop nop nop nop nop nop * Summary of magic key sequences 101 keyboard84 keyboard function Ctrl-Alt-Delete Ctrl-Alt-Delete reboot Ctrl-Alt-EscCtrl-Alt-Escdebug Ctrl-Alt-Space Ctrl-Alt-Space susp ScrollLock ScrollLock slock PrintScreen Shift-(Numpad *)/PrintScreennscr Ctrl-PrintScreenShift-Ctrl-(Numpad *)/PrintScreen debug Alt-PrintScreen/SysRq SysRq
Re: keymaps
What's wrong with us.unix.kbd? This also swaps a bunch of other things - Grave-Esc, BS-Del, etc. It was more confusing, so I made a new keymap. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: keymaps
my vote: A version of the standard keymap with CapsLock and LeftCtl functio ns swapped so the control key is under my left finger like God intended! My vote is both of the above. I've never found a use for CapsLock, but LeftCtl is important enough that I wouldn't mind it duplicated. Most people I know are like this. (Yes of course there needs to be a way to get at capslock for those who really need it) I understand many of you prefer the Ctrl key sitting next to the 'A' key, as my own keymap swaps the Caps key and the Left Ctrl key too :-) But, this is a matter of personal taste and preference which you can easily obtain by editing a keymap. Gentlemen, I don't intend to add yet another keymap to /usr/share/syscons/keymaps. I am merely trying to define a reasonable set of common, consistent key binding for existing keymaps. National keyboards have different layout of regular keys. But function keys and special keys are placed identically. They should work in the same way, or at least similar way in all keyboards, unless there is a good reason to do otherwise. (I am not talking about non-AT keyboards which are totally different from either AT 84 or 101/102/104 keyboards.) What I want to avoid is that one key does one thing on one national keyboard and the same key on another national keyboard does a different thing. This is absurd, and hazardous when writing document or giving advises (you can cycle through vtys by hitting PrintScreen, um, well, on most keyboards, well, on your keyboard you may need to hit a different key, I don't know which...) In order to define a common set, I start from key assignments based on existing keymaps, which may not necessarily be your, or my, favorite. (Why on earth Ctrl-Alt-ESC yields debug? Because someone started it and documented in the handbook!) New functions and their assignments can be controversial and we shall hear various opinions about them. I expect that, and we should resolve this on technical merits. (The following is an example. In my previous post I removed the backscroll function from the Pause key because the ScrollLock key already has backscroll. My reasoning was wrong. A user reported that his notebook PC doesn't have the ScrollLock key and we have to let the Pause key have backscroll too.) I don't intend to enforce preference or taste, or particular usage of, or a particular way of working with the keyboard. (I certainly won't force mine on you) So, keymaps I am trying to define may look too plain, too boring, too uninteresting, and less appealing to you. But, I am not depriving you of liberty to modify your keymap. Be creative and write a keymap of your own. You are free to do that. But, don't expect your modification should instantly be the standard in all keymaps. It won't necessarily happen... Well, it might happen, if it has sound reason other than because I like it that way :-) Kazu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: keymaps
On Fri, 22 Jan 1999, Kazutaka YOKOTA wrote: Gentlemen, I don't intend to add yet another keymap to /usr/share/syscons/keymaps. I am merely trying to define a reasonable set of common, consistent key binding for existing keymaps. National keyboards have different layout of regular keys. But function keys and special keys are placed identically. They should work in the same way, or at least similar way in all keyboards, unless there is a good reason to do otherwise. (I am not talking about non-AT keyboards which are totally different from either AT 84 or 101/102/104 keyboards.) What would be useful here is the ability to compose keymaps. There would be basically two sets: one that defines the layout of the main keyboard and one that defines the layout of the other keys. That way I could pick my dvorak layout, then add on a layout that, say, swaps control and caps lock but leaves the main layout alone. -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: keymaps
-Original Message- From: John Fieber [mailto:jfie...@indiana.edu] Sent: Friday, January 22, 1999 3:51 PM To: Kazutaka YOKOTA Cc: curr...@freebsd.org Subject: Re: keymaps On Fri, 22 Jan 1999, Kazutaka YOKOTA wrote: Gentlemen, I don't intend to add yet another keymap to /usr/share/syscons/keymaps. I am merely trying to define a reasonable set of common, consistent key binding for existing keymaps. National keyboards have different layout of regular keys. But function keys and special keys are placed identically. They should work in the same way, or at least similar way in all keyboards, unless there is a good reason to do otherwise. (I am not talking about non-AT keyboards which are totally different from either AT 84 or 101/102/104 keyboards.) What would be useful here is the ability to compose keymaps. There would be basically two sets: one that defines the layout of the main keyboard and one that defines the layout of the other keys. That way I could pick my dvorak layout, then add on a layout that, say, swaps control and caps lock but leaves the main layout alone. I was thinking something similar, a way to dynamically modify the map ala xmodmap would be useful so that users who have particular preferences can implement the changes in, say, .login That's exactly what I do with xmodmap and X. The standard maps can continue to reflect the actual layout of the keyboards then rather than having a number of variations according to popular user preference. Paul To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
keymaps
I recently looked at keymaps in /usr/share/syscons/keymaps and found many minor errors. In addition to that, there is so much inconsistency among existing keymaps. True that national keyboards have different layout of regular keys (alphanumeric keys and symbol keys). But, it is absurd that functions keys and special keys are handled in so many different ways. The syscons keymap can assign special functions to key strokes, such as `suspend', `next virtual screen'. However, some keymaps don't have these special functions assigned to any key strokes. The other keymaps may have them but assign them differently. There is no standard here. So, I would propose the following key assignment to be the standard from now on. I compiled this list based on existing keymaps and recent input from a contributer (thanks, J M Alcaide!) If this assignment is not desirable for some keymaps, such as Russian and Dvorak maps which are rather unique, they may be made exceptions. But, unless there is a good reason to make other exceptions, I will modify the other national keymaps to adapt these key assignments. Any comments? I am open to suggestions. Kazu * 101/102/104 Enhanced Keyboard support Key CodeKey Stroke Function - 1 Ctrl-Alt-EscEnter DDB (debug). 57 Ctrl-Alt-Space Suspend (susp). 70 ScrollLock Backscroll (slock). 84 Alt-SysRq(PrintScreen) - (nop) 92 PrintScreen Switch to the next vty (next). 104 Pause Start screen saver (saver). 104 Alt-Pause Suspend (susp). 105 Left Windowsfkey62 106 Right Windows fkey63 107 Menufkey64 108 Ctrl-Break(Pause) Enter DDB (debug). The separate SysRq key doesn't exist on the enhanced keyboard. It is combined with the PrintScreen key. The SysRq code is generated when the Alt and the PrintScreen keys are pressed together. The separate Break key doesn't exist on the enhanced keyboard. It is combined with the Pause key. The Break code is generated when the Ctrl and the Pause keys are pressed together. The above assignments for the keycodes 1, 57, 70, 84 and 92 are compatible with many, if not all, existing keymaps. The assignments for 104 and 108 are new. Many keymaps lacks entries for 105 through 107. * 84 Keyboard support Key CodeKey Stroke Function - 1 Ctrl-Alt-EscEnter DDB (debug). 57 Ctrl-Alt-Space Suspend (susp). 70 ScrollLock Backscroll (slock). 84 SysRq - (nop) 92 Shift-PrintScreen(*)Switch to the next vty (next). 104 Ctrl-Pause(NumLock) Start screen saver (saver). 104 Ctrl-Alt-Pause(NumLock) Suspend (susp). 108 Ctrl-Break(ScrollLock) Enter DDB (debug). The separate PrintScreen key doesn't exist on the 84 keyboard. It is combined with the numpad * key. The PrintScreen code is generated when the Shift and the numpad * keys are pressed together. The separate Pause key doesn't exist on the 84 keyboard. It is combined with the NumLock key. The Pause code is generated when the Ctrl and the NumlLock keys are pressed together. The separate Break key doesn't exist on the 84 keyboard. It is combined with the ScrollLock key. The Break code is generated when the Ctrl and the ScrollLock keys are pressed together. * Proposed keymap Combining the support for the 84 keyboard and the enhanced keyboard described above, we will get the following keymap entries. alt ctrlalt alt ctrl code base shift ctrl shift alt shift ctrl shift - 1 esc esc esc esc esc esc debug esc 57 ' ' ' ' null ' ' ' ' ' ' susp ' ' 70 slock slock slock slock slock slock slock slock 84 nop nop nop nop nop nop nop nop 92 next next nop nop nop nop nop nop 104 saver nop saver nop susp nop susp nop 105 nop nop nop nop nop nop nop nop 106 nop nop nop nop nop nop nop nop 107 nop nop nop nop nop nop nop nop 108 nop nop debug nop nop nop nop nop EOF To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: keymaps
Kazutaka YOKOTA wrote: * 101/102/104 Enhanced Keyboard support Key CodeKey Stroke Function - 1 Ctrl-Alt-EscEnter DDB (debug). 57 Ctrl-Alt-Space Suspend (susp). 70 ScrollLock Backscroll (slock). 84 Alt-SysRq(PrintScreen) - (nop) 92 PrintScreen Switch to the next vty (next). 104 Pause Start screen saver (saver). 104 Alt-Pause Suspend (susp). 105 Left Windowsfkey62 106 Right Windows fkey63 107 Menufkey64 108 Ctrl-Break(Pause) Enter DDB (debug). I am afraid of being myself the cause of a keymap revolution!! 8-) As I said in a previous message to freebsd-bugs, I think that mapping the saver to the base Pause key could annoy people accustomed to pressing this key to stop the screen output. I would map the [very useful] saver function to Shift-Pause (Shift-Ctrl-NumLock on the 84 KB ?) or, perhaps better, Break (Ctrl-Pause on the 104 KB, Ctrl-ScrollLock on the 84 KB). Another suggestion: I would move the debug function from Break to SysReq (Alt-PrtScr on the 104 KB); I think that associating SysReq to the debugger is intuitive. Then, the now free Break key could be used for the saver function (as suggested above) or, perhaps, the DOS-like etx (Ctrl-C) character (I'm supposing the usual stty intr ^C). * 84 Keyboard support Key CodeKey Stroke Function - 1 Ctrl-Alt-EscEnter DDB (debug). 57 Ctrl-Alt-Space Suspend (susp). 70 ScrollLock Backscroll (slock). 84 SysRq - (nop) 92 Shift-PrintScreen(*)Switch to the next vty (next). 104 Ctrl-Pause(NumLock) Start screen saver (saver). 104 Ctrl-Alt-Pause(NumLock) Suspend (susp). 108 Ctrl-Break(ScrollLock) Enter DDB (debug). The separate PrintScreen key doesn't exist on the 84 keyboard. It is combined with the numpad * key. The PrintScreen code is generated when the Shift and the numpad * keys are pressed together. The separate Pause key doesn't exist on the 84 keyboard. It is combined with the NumLock key. The Pause code is generated when the Ctrl and the NumlLock keys are pressed together. The separate Break key doesn't exist on the 84 keyboard. It is combined with the ScrollLock key. The Break code is generated when the Ctrl and the ScrollLock keys are pressed together. * Proposed keymap Combining the support for the 84 keyboard and the enhanced keyboard described above, we will get the following keymap entries. alt ctrlalt alt ctrl code base shift ctrl shift alt shift ctrl shift - 1 esc esc esc esc esc esc debug esc 57 ' ' ' ' null ' ' ' ' ' ' susp ' ' 70 slock slock slock slock slock slock slock slock 84 nop nop nop nop nop nop nop nop 92 next next nop nop nop nop nop nop 104 saver nop saver nop susp nop susp nop 105 nop nop nop nop nop nop nop nop 106 nop nop nop nop nop nop nop nop 107 nop nop nop nop nop nop nop nop 108 nop nop debug nop nop nop nop nop There is something I do not understand. Is it possible to generate the Ctrl-Key104 and Alt-Ctrl-Key104 combinations? These are not available on the 104 KB (Ctrl-Pause == Break) and, on the 84 KB, Ctrl-NumLock yields the base Pause (or Ctrl-Pause?)... Another question: the numpad '*' key (keycode 55) has this mapping in most keymaps: 055 '*''*'nscr nscr '*''*'nscr nscr You told me that the nscr function was needed for the 84 KBD, but now you are saying that, on that KB, the PrtScrn code (92) is generated by Shift-Numpad*. Now I cannot understand the utility of that mapping for the keycode 055... --JMA --- José Mª Alcaide | mailto:j...@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 --- Go ahead... make my day. - H. Callahan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: keymaps
Kazutaka YOKOTA wrote: : 104 Pause Start screen saver (saver). : The above assignments for the keycodes 1, 57, 70, 84 and 92 are compatible with many, if not all, existing keymaps. So far so good! The assignments for 104 and 108 are new. 104 (Pause?) does the Backscroll on my Libretto 70. I'd hate to lose that. M To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: keymaps
104 Pause Start screen saver (saver). : The above assignments for the keycodes 1, 57, 70, 84 and 92 are compatible with many, if not all, existing keymaps. So far so good! The assignments for 104 and 108 are new. 104 (Pause?) does the Backscroll on my Libretto 70. I'd hate to lose that. ScrollLock does back scroll too. You want both? Kazu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: keymaps
my vote: A version of the standard keymap with CapsLock and LeftCtl functions swapped so the control key is under my left finger like God intended! Greg, home of us.iso-lock-ctl.kbd To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: keymaps
In message 199901220043.laa22...@lightning.itga.com.au Gregory Bond writes: : my vote: A version of the standard keymap with CapsLock and LeftCtl : functions swapped so the control key is under my left finger like : God intended! What's wrong with us.unix.kbd? Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: keymaps
On Fri, 22 Jan 1999, Gregory Bond wrote: my vote: A version of the standard keymap with CapsLock and LeftCtl functions swapped so the control key is under my left finger like God intended! My vote is both of the above. I've never found a use for CapsLock, but LeftCtl is important enough that I wouldn't mind it duplicated. Most people I know are like this. (Yes of course there needs to be a way to get at capslock for those who really need it) -- http://www.black-hole.com/users/henrymiller/ h...@black-hole.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: keymaps
Kazutaka YOKOTA wrote: ScrollLock does back scroll too. You want both? My Libretto 70CT has no Scroll Lock, only a Pause. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: keymaps
On Fri, Jan 22, 1999 at 11:43:56AM +1100, Gregory Bond wrote: my vote: A version of the standard keymap with CapsLock and LeftCtl functions swapped so the control key is under my left finger like God intended! Take your existing keymap and swap 029 and 058 with these: 029 clock clock clock clock clock clock clock clock O 058 lctrl lctrl lctrl lctrl lctrl lctrl lctrl lctrl O I've tacked this into my Dvorak keymap and have been pretty happy ever since --- it actually makes the console usable. -- Brian Cully sh...@rcn.com ``I'm not surprised,'' said I. ``You created God in your own image, and when you found out he was no good you abolished him. It's quite a common form of psychological suicide.'' -- Robertson Davies, Fifth Buisiness To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
