On Mon, 19 Mar 2001, Tom Roche wrote: > So, although 'unset' doesn't make .sh_history, or its successor, go > away upon _utterance_, it does appear to make it go away upon > _exit_-- which IIRC is better than what we had, and mostly solves > the problem of the ever-growing .sh_history (except for very long > tramp sessions). (Note that .history is made by my csh session, not > ksh.) What happens when you do it the second time? Do you then get large .sh_history files, too? I'd suppose that once you delete the .sh_history file and then make sure that ksh doesn't save it again, Bob would be your uncle. kai -- Be indiscrete. Do it continuously.
- .sh_history problem Tom_Roche
- Re: .sh_history problem Kai Gro�johann
- Re: .sh_history problem Tom_Roche
- Re: .sh_history problem Kai Gro�johann
- Re: .sh_history problem Tom_Roche
- Re: .sh_history problem Kai Gro�johann
- Re: .sh_history problem Tom_Roche
- Re: .sh_history problem Kai Gro�johann
- Re: .sh_history problem Tom_Roche
- Re: .sh_history problem Kai Gro�johann
- Re: .sh_history problem Tom_Roche
- Re: .sh_history problem Kai Gro�johann
- Re: .sh_history problem Tom_Roche
- Re: .sh_history problem Kai Gro�johann
- Re: .sh_history problem Pete Forman
- Re: .sh_history problem Kai Gro�johann
- Re: .sh_history problem Pete Forman
- Re: .sh_history problem Ted Stern
- Re: .sh_history problem Tom_Roche
- Re: .sh_history problem Tom_Roche
