On 6/13/11 1:10 PM, Bradley M. Kuhn wrote:
> The only feature you describe above missing with that configuration is
> that existing shells won't find history commands written out
> in-between. I have a tendency to close/open bash shells, so I don't run
> into that problem.
>
> Unfortunately, having looked recently at the history code, I think
> adding a feature whereby existing running shells "notice" the history
> file has changed would be a large rewrite to the history code. I think
> that would be a useful optional feature, though.
People have had success using `history -a' and `history -n' to accomplish
this. The idea is to append your latest command to some common history
file, then use history -n to read other shells' commands into your
history list.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
