HISTFILESIZE
The maximum number of lines contained in the history file. When this variable is assigned a value, the history file is truncated, if necessary, by removing the
oldest entries, to contain no more than that number of lines. The default value is 500. The history file is also truncated to this size after writing it when
an interactive shell exits.
. . .
HISTSIZE
The number of commands to remember in the command history (see HISTORY below). The default value is 500.
HISTSIZE commands are kept "online" in an interactive session, whilst up to HISTFILESIZE commands will be saved between sessions. The set history doesn't ring a bell.
I tried looking for the answer online and came up with only a few semi-answers as to why file and directory names are case sensitive in Unix. Right off the bat, I'll say this doesn't bother me. But I run into tons of Windows and OpenVMS admins in my day job who go batty when they have to deal... (3 Replies)
When I checked with top command, I found tht my buffers are always 137M, which means that they are sort of overloaded. My Inactive memory is 520M. Is it possible to increaase the buffer size and what would be the command for that? (0 Replies)
HI! All
Iam facing an issue with split comman in unix
Prifix=Z_PRICE_NEW`date "+%Y%m%d%H%M%S"`
split -5000 Product.txt $Prifix
find . -name "$Prifix*" -print | {
while read FILE;
do
mv $FILE $FILE.txt
done
}
when is execute the comman the command is working fine and generating the... (2 Replies)
i run history command and I want to eliminate the list number.
So far this perl script works as long as the list is a exact 3 character
long.
cat dd | perl -pe 's,\d{3},,'
70 export JAVA_HOME=.
81 export JAVA_HOME=.
82 export JAVA_HOME=`pwd`
export JAVA_HOME=`pwd`
... (1 Reply)
hi all i got a assignment but this is part of it only..
i need the logic that all..
below is the kind of output that i want to get.
1
12
123
1234
12345
2345
345
45
5
i noe i need to use for loop cos currently i am doing a short cut way which is (1 Reply)
Hi Gurus
I want to know the command & tips regarding, how to increase or decrease inode number of the particular ufs filesystem. Is it possible to do it in a live/production environment.
Regards (3 Replies)
% history clean
history: Badly formed number. :(
% echo $0
/usr/local/bin/tcsh
% uname
SunOS
% grep -e "hist" .tcshrc.user
set history=90
set savehist=80
Please suggest what could be the problem here. Thanks in advance. (1 Reply)
Hi,
I did compiled net-snmp with a value of MAXLOGMATCH 1000. Now I need to monitor more then 1000 strings on my server. I've entered the lines in smpd.conf but they are being ignored. Only upto 1000 lines are being checked. Can I increase the value of MAXLOGMATCH without recompiling? (0 Replies)
Hi
I am trying to increase the number of commands recorded in my .bash_history file.
I followed what is indicated and have add to my .bashrc
export HISTCONTROL=ignoreboth
export HISTSIZE=1000000
export HISTFILESIZE=1000000
export HISTIGNORE='ls'but the .bash_history only contains 690... (5 Replies)
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)