UNIX for Dummies Questions & Answers

Is it possible to use the keyboard UP ARROW in place of [esc]k to recall history? If so, how/what do I need to do change terminal emulation, etc.?

TIA,
George

yes. don't set -o vi and that should do it.

Nope that doesn't do it.

Hi.

Saying:
is not very definitive. For example, what did it seem to do? Was anything else affected?

On a machine running:

Code:

OS, ker|rel, machine: AIX, 1, 000641284C00

my experience is that, for Gnome terminal doing an ssh to the remote machine and running there in bash:

Code:

set +o vi

turns off the arrow feature, resulting in a display like:

Code:

^[[A^[[A

whereas:

Code:

set -o vi

enables the arrow function.

However, there are many variables that might come into play here, settings from stty, the terminal emulator you are using, and so on.

Good luck ... cheers, drl

issuing command set -o vi enables recall using [esc]k, but not the keyboard arrows. Without issuing the cmd there is NO recall. system is AIX 5.3 & putty emulator. It doesn't matter which terminal option I emulate, all give the same response.

Hi.

I cannot easily get to the aix system from a putty client. However, we might be able to whittle down the number of possible issues. Please post the results of these commands from the prompt (the dollar is the prompt for me). After the command are listed the responses I get:

Code:

$ ps | grep $$
 33228  pts/5  0:00 grep 42706 
 42706  pts/5  0:00 -bash

Code:

$ uname -a
AIX aix 1 5 000641284C00

Code:

$ bash --version
GNU bash, version 3.00.16(1)-release (powerpc-ibm-aix5.1)
Copyright (C) 2004 Free Software Foundation, Inc.

Code:

$ echo $TERM
xterm

Code:

(enter the up arrow followed by the down arrow)
$ ^[[A^[[B

cheers, drl

ps | grep $$
50834 pts/0 0:00 grep 52940
52940 pts/0 0:00 -ksh

uname -a
AIX DCHS-PINT-002 2 5 00C5D86F4C00

echo $TERM
xterm

the up & down arrows merely result in 2 beeps. I set the TERM variable to vt100 which was what my putty session was set to but that didn't change anything.

I also discovered that the system is running ksh natively NOT bash.