01-01-2006
I suggest that you maintain a history file to keep track of the past commands, something like what ksh maintains. The file is .sh_history or something similar in the user's home directory. There is another thing that you would have to do, and that is have an escape sequence by which the user enters the history mode. Ksh in vi mode uses Esc to enter the command mode; you have to use something similar.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi techies,
I have a doubt upon the command history utilities in Unix ...
As far as I know, history stores the event number and command for upto
that many number of previous commands executed in the HISTSIZE variable ... my doubt here is can we get the time in which these commands were... (3 Replies)
Discussion started by: Sabari Nath S
3 Replies
2. Solaris
is there any way to determine the last command entered on a unix machine???
Thanx (3 Replies)
Discussion started by: mm00123
3 Replies
3. Shell Programming and Scripting
Hi, I'm new to UNIX shell programming... can anyone help in doing the following :
1) create a text file named "Model File" having following columns :
Name Number Physics Chemistry
2) prompt user to n rows enter the name, number, physics ,chemistry
3) display the entire columns and rows... (1 Reply)
Discussion started by: Mayuri P R
1 Replies
4. UNIX for Dummies Questions & Answers
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
5. Programming
hii to all
i am developing a simple unix shell in c i want to add history feature in that how could i do that plz help if there is any tutorial or website plz put it here
history feature should be like that in bash, when press up key show the previous command typed in console
plz be... (1 Reply)
Discussion started by: vipin_jss
1 Replies
6. Shell Programming and Scripting
please help me to execute a simple shell script like
for i in `ls
echo $i
done
. i dont want to create a new sh file to execute it. Can i just type and execute it ? because I always this kind of simple for loops .
Please help .
Thanks (7 Replies)
Discussion started by: Sooraj_Linux
7 Replies
7. Shell Programming and Scripting
Hello :)
I'm a newb when it comes to shell scripting and was wondering about a command(s) for a script that could be used to checkout a certain number of version/revision histories of a file. I know for the latest revison you "co filename" or for a certain revision number "co -r*.* filename"... (2 Replies)
Discussion started by: MN-DBA
2 Replies
8. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Write a shell script that accepts two arguments. The two arguments are the
name of 2 files.
• If the arguments... (3 Replies)
Discussion started by: Scripter12345
3 Replies
9. What is on Your Mind?
I am pleased to announce this new video in 1080 HD for UNIX lovers honoring thirty years of UNIX history spanning from 1969 to 1999 presented in 150 seconds (two and a half minutes) in 1080 HD, celebrating the 50th anniversary of UNIX.
The Great History of UNIX (1969-1999) | 30 Years of UNIX... (8 Replies)
Discussion started by: Neo
8 Replies
LEARN ABOUT OSX
tklib_history
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)