09-01-2011
Tux-HJKL as arrow keys
I would like to configure the key combination Tux-J (Win-J) as Down Arrow, and the rest of the VIM-style movement keys as well (HKL). What is the best way to do this so that it will work in all applications? I thought about editing the keyboard layout but I'm not sure how to do that for Tux-key combinations.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hey Guys ,
How do we trap the arrow keys in shell programming.
Or atleast can we read the ascii code of the arrow keys.
I want to read the arrow keys pressed by the user
and accordingly highlight the corresponding menu option.
Is it possible in shell to do so ??
... (1 Reply)
Discussion started by: nageshrc
1 Replies
2. UNIX for Dummies Questions & Answers
how to use the arrow keys in shell scripting. is there any special synatax / command for this.
i just want to use the arrow keys for navigation.
replies appreciated
raguram R (3 Replies)
Discussion started by: raguramtgr
3 Replies
3. Shell Programming and Scripting
I would like to get a script to respond to arrow key presses to scroll up and down a menu.
The platform is CDLinux which uses a prehistoric version of bash, version 1.14.7.
I would like to do something like "read -sn 1 keyin" but the "read" command is so primative that it only has the -r... (1 Reply)
Discussion started by: simonb
1 Replies
4. Solaris
Hello,
I am unable to use the arrow keys in some applications. For example, in bash, I am able to use the arrow keys to to go back and forth characters in current line and search the history--I can do everything you'd expect to be able to do with the arrow keys. However, in bc, I cannot use... (4 Replies)
Discussion started by: cooldude
4 Replies
5. UNIX and Linux Applications
hi,
can anyone tell me how to enable arrow keys to scroll thru the commands on command prompt.
I am using C shell ( I know, in k shell, set -o vi would enable vi command history, but set -o doesnte exist in c shell) (4 Replies)
Discussion started by: hemangi13
4 Replies
6. UNIX for Dummies Questions & Answers
Hi
I am working on SunOS 5.10 from remote terminal using putty.
Also
echo $TERM
xterm
In vi editor when in insert mode arrow keys are not working for cursor movement instead they print A B C and D.
Please help.
thanks
ravs (7 Replies)
Discussion started by: ravashingravi
7 Replies
7. Shell Programming and Scripting
I recently needed to collect arrow keys (and function keys etc.) in a shell script so that I could run a text graphics-style data entry system (with text entry fields, drop-down list boxes, progress bars and the like). Yes you can do all this in shell, and portably too if you're careful.
I've... (4 Replies)
Discussion started by: cambridge
4 Replies
8. Shell Programming and Scripting
hello everybody,
as many, I have a problem with a script...
I wrote a shell script in which I want to read a variable value. the problem is that I can't use the arrow keys.
Here is the script I use :
#!/bin/bash
stty erase ^H
read foune
echo "$foune"
exit 0;
the problem is... (2 Replies)
Discussion started by: Moumou
2 Replies
9. UNIX for Advanced & Expert Users
Hi,
I'm having a problem with my ssh link to various Sun servers running Solaris 9 and 10 from an Windows XP box running Cygwin/X.
I am using ssh to connect to a number of different Sun servers. My problem is that when editing a remote shell command line with the arrow direction keys the... (0 Replies)
Discussion started by: stv_t
0 Replies
10. UNIX for Dummies Questions & Answers
Would somebody advise how arrow keys could be binded in AIX v5.3?
I could not find reasonable information online related to AIX.
I've meat advises to define:
alias __A=$'\020' # or the same: alias __A=$(echo "\020")
alias __B=$'\016'
alias __C=$'\006'
alias __D=$'\002'
But it does... (2 Replies)
Discussion started by: alex_5161
2 Replies
LEARN ABOUT OSF1
sys_attrs_gpc_input
sys_attrs_gpc_input(5) File Formats Manual sys_attrs_gpc_input(5)
NAME
sys_attrs_gpc_input - gpc_input subsystem attributes
DESCRIPTION
This reference page lists and describes attributes for the GPC Input (gpc_input) kernel subsystem. This subsystem handles mouse and key-
board input for both old style LK* keyboards and serial mice, and the newer PC-style (PS/2) keyboards and mice. In all supported scan code-
sets, unique single-byte scan codes differentiate the standalone Insert, Home, Page Up, Page Down, Delete, and End keys from the same keys
on the numeric keypad (with Num Lock toggled to off).
Refer to the sys_attrs(5) reference page for an introduction to the topic of kernel subsystem attributes.
The gpc subsystem has a number of visible attributes. Of these, only the following should ever be modified:
A value that identifies the scan codeset generated by the keyboard. Only two values are supported for this attribute. The scan code-
sets that these values identify differ in how internal keyboard hardware distinguishes between the numeric keypad's Up Arrow
(entered with with Num Lock toggled off) and the standalone Up Arrow key. Keyboard hardware sends different single-byte scan codes
to distinguish the standalone Up Arrow and the Up Arrow entered through the numeric keyboard (with Num Lock toggled off). Keyboard
hardware sends two bytes for the standalone Up Arrow and a single-byte scan code for the Up Arrow entered through the numeric key-
board.
These values are intended to be set by system software, not users. Although both values (scan codesets) work with most of the Compaq
keyboards (both LK* and PC-style) used with Tru64 UNIX systems, 3 identifies the scan codeset that is most efficient for these key-
boards. The keyboard of the AlphaBook (laptop) computer is the only supported keyboard that requires the 2 setting. The scan code-
sets identified by these values may work with other (third-party) keyboards; however, Compaq does not test or support other key-
boards for use with Tru64 UNIX systems.
It is possible to set kbd_scancode to a 0 or 1 value. These values are currently undefined and will result in one of the following
console errors:
gpc_input_configure: scan code not supported
ps2_input_configure: scan code not supported
These errors are displayed independently of the setting for the gpc_developer_debug attribute.
Enables (1) or disables (0) boot- and run-time console messages used by systems programmers to debug device driver configuration
problems.
Default value: 0 (disabled)
SEE ALSO
sys_attrs(5)
sys_attrs_gpc_input(5)