Re: [4.0.2 bug] commands not written to history

["Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>]

On Jul 12,  1:59am, Vincent Lefevre wrote:
} Subject: Re: [4.0.2 bug] commands not written to history
}
} There is another problem. For instance, when I want to backward-search
} for `file.', nothing is found, though there is a matching line in the
} history:
} 
} greux:~out> grep "zip -r" $HISTFILE                                    <1:48:28
} : 994891028:0;zip -r file.zip *
} : 994895233:0;grep "zip -r" $HISTFILE
} greux:~out> grep "zip -r" $HISTFILE                                    <1:48:29
} failing bck-i-search: file._

Hrm.  Just because there's an entry in $HISTFILE doesn't mean that it's
present in the shell history, of course.  With INC_APPEND_HISTORY set
(as I believe you have), $HISTFILE may have up to $[SAVEHIST/5] extra
commands stored in it.  (This is to avoid having to rewrite the entire
file too frequently.)  But only $HISTSIZE of those commands is actually
in memory (and thus searchable) at any given time.

Next time you see this happen, try running `fc -W temphistfile' and then
`diff $HISTFILE temphistfile'.  You should see differences only at the
beginning and possibly one or two commands at the end, not in the middle.
If there are commands missing (or misordered) in the middle, then we'll
have evidence of a real bug.
 
} It seems to be due to the fact that the time stamps are not in the
} increasing order.

Can you show an example of this, please?

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net