Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!sdd.hp.com!hp-pcd!hpfcso!hpfcmdd!hpbbrd!hpbbn!hpcc01!hpcuhb!hpcllla!hpclove!defaria
From: defaria@hpclove.HP.COM (Andy DeFaria)
Newsgroups: comp.sys.hp
Subject: Re: Re: .sh_history explodes...
Message-ID: <3770059@hpclove.HP.COM>
Date: 1 Aug 90 16:47:23 GMT
References: <4@gauss.mmlai.UUCP>
Organization: Hewlett Packard Calif. Language Lab
Lines: 22

What I do is:

export HISTFILE=/nonexistant/file # make history unique per window

Since the HISTFILE is nonexistant ksh will keep the history file in a
temporary nameless file (inode only) so I don't have to worry about a
.sh_histroy file growing too big.  As a side benefit (or problem depending on
how you view it) each hpterm window has its own history file so if I type

echo "This echo command was entered in my console window"

then I go to a regular terminal window and C-p (emacs style for "get last
command".  Vi style would by ESC then a "k") I will not get the preceeding
echo command but whatever was my preceeding command in this hpterm window.
There are some advantages with sharing a .sh_history file (the ability to
easiliy redo a command that was entered into the wrong window, but I can
always cut and paste) but I tend to think of each terminal window as its own
entity with its own redo stack.

The only other problem I can see it that you won't be able to save your redo
stack from login to login but you're really not logging in when your using X.
At least the way I view it.