Hi,
Can we display the Date/time stamp in history command
Ex:
$history
output
-----------
vi pr.sh
ksh -x pr.sh
ksh -n pr.sh
nhoup ksh pr.sh &
nohup ksh pr.sh &
i want the output like this
Tue Mar 14 17:18:57 GMT 2006 vi pr.sh HOSTNAME
is it possible sir ???? (3 Replies)
Hi All.
Suppose I am in a "verylongpath" directory and I type "gedit thisfile".
At a later stage, the command is accessible from the hystory, but it is
useless if I have moved to another directory. The same applies to
"cd myfolder", etc.
Is there a way to instruct shell history to... (1 Reply)
Can anyone tell this:
If two users are logged into the same server from different locations. Is there a way to see the history command of the other user? I tried the history command, but it is showing me only the commands I used.
Thanks in advance for your help.
Iamnew2solaris (1 Reply)
hi
i want to show my history command in UNIX solaris ( bash shell ),,
i tried this command ( HISTTIMEFORMAT="%d/%m/%y %T " )
but it's not working with me ,, is there any restricted condition to do this command
any one know why it's not working to me ..
thanks (10 Replies)
hi unix expert
how can i see the history of command that i entered in past?
history (1 Reply)
Discussion started by: abdossamad2003
1 Replies
LEARN ABOUT MOJAVE
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)