On Wed, Aug 31, 2011 at 02:13:19PM +0200, LEVAI Daniel wrote: > On Wed, Aug 31, 2011 at 06:57:34 -0500, Marco Peereboom wrote: > > On Wed, Aug 31, 2011 at 11:59:29AM +0200, LEVAI Daniel wrote: > > > On Tue, Aug 30, 2011 at 13:55:57 -0500, Marco Peereboom wrote: > > > > On Tue, Aug 30, 2011 at 11:11:46AM -0500, Marco Peereboom wrote: > > > > > I have had enough of corrupt ksh history so I had a look at the code > > > > > to > > > > > try to fix it. The magical code was very magical so I basically > > > > > deleted > > > > > most of it and made ksh history into a flat text file. It handles > > > > > multiple ksh instances writing to the same text file with locks just > > > > > like the current ksh does. I haven't noticed any differences in > > > > > behavior running this. > > > > > > If one had set HISTFILE='', the old behaviour was to not write a history > > > file, but the "in memory" history was still working. > > > With this patch, if I set HISTFILE='' then there will be no command > > > history at all. > > > > This is the same with current ksh. > > Not for me. Currently if I set HISTFILE to '' then in-memory history > works but it doesn't write to history file (which was my intention when > I've set HISTFILE='').
Hmmm, I tried again and now I see it. I blame it on not enough coffee. Thanks I'll go figure it out. > > > Daniel > > -- > LIVAI Daniel > PGP key ID = 0x83B63A8F > Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
