Sponsored Content
Operating Systems SCO BASH-like feature. is possible ? Post 40702 by davidg on Monday 22nd of September 2003 01:40:11 AM
Old 09-22-2003
Hi,

Most of the shells can use the arrow keys. Korn-shell (standard on your OS) can do it as well. It's just a matter of telling him to do.

"set -o vi" will set him in vi mode
"set -o emacs" will set him in emacs mode.

I think vi mode will get the most close to your needs. Maybe someone else knows the best option for you. (Don't know how bash exact works)

Regs David

P.S. : If it is your job to maintain a server, I'dd defintly choose for h,j,k and l. What happens if your server dies and you should boot up in single user mode? First install bash?
 

4 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

does anybody know what the bcb feature is in EMC?

does anybody know what the bcb feature is in EMC? (5 Replies)
Discussion started by: jigarlakhani
5 Replies

2. HP-UX

is this an 11.31 feature? cpu sequence...

we got our first Itanium server, and was wondering if the cpu sequence listed below is normal? rx8640, running 11.31 System: myBOX Tue Mar 25 07:21:45 2008 Load averages: 0.00, 0.00, 0.00 219 processes: 187 sleeping, 31 running, 1 zombie Cpu... (2 Replies)
Discussion started by: mr_manny
2 Replies

3. UNIX for Dummies Questions & Answers

History feature in Unix

Hi, I'm working on two flavours of unix namely HP-UX and sun solaris. In HP-UX, for executing the previous commands, i use the arrow keys. But on sun solaris this is not working. Can anyone explain how to use history feature effectively in sun solaris os? Thanks (4 Replies)
Discussion started by: venkatesht
4 Replies

4. UNIX for Beginners Questions & Answers

To send ID and Password for each command using expect feature in bash script

Dear Tech Guys, I am trying to send some commands on the local server and it always asks for user name and password after each command. To serve the purpose I am using expect function as follows: #!/usr/bin/expect set timeout 20 spawn "./data1.sh" expect "Please Enter UserName: "... (6 Replies)
Discussion started by: Xtreme
6 Replies
history(n)					       Provides a history for Entry widgets						history(n)

__________________________________________________________________________________________________________________________________________________

NAME
history - Provides a history for Entry widgets SYNOPSIS
package require Tcl 8.4 package require Tk 8.4 package require history ?0.1? ::history::init pathName ?length? ::history::remove pathName ::history::add pathName text ::history::get pathName ::history::clear pathName ::history::configure pathName option ?value? bell _________________________________________________________________ DESCRIPTION
This package provides a convenient history mechanism for Entry widgets. The history may be accessed with the up and down arrow keys. ::history::init pathName ?length? Arranges to remember the history of the named Entry widget. An optional length determines the number of history entries to keep. This may be changed later with ::history::configure. History entries must be added with the ::history::add command before they can be seen. ::history::remove pathName Forgets all history entries for the Entry pathName and removes the history bindings. ::history::add pathName text This command is used to add history entries to an Entry that has previously had ::history::init called on it. This command should be called from your Entry handler with the contents of the entry (or whatever you wish to add to the history). ::history::get pathName This command returns a list containing the history entries for the Entry pathName ::history::clear pathName This command clears the history list for the named Entry. ::history::configure pathName option ?value? This command queries or sets configuration options. Currently the options recognized are length and alert. Setting the length deter- mines the number of history entries to keep for the named Entry. Alert specifies the command to run when the user reaches the end of the history, it defaults to bell entry .e bind .e <Return> [list ProcessEntry %W] ::history::init .e pack .e proc ProcessEntry {w} { set text [$w get] if {$text == ""} { return } ::history::add $w $text puts $text $w delete 0 end } KEYWORDS
entry, history history 0.1 history(n)
All times are GMT -4. The time now is 10:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy