Re: What was the reason for history -D not reporting runtimes?

["Nikolai Weibull" <now@xxxxxxxx>]

On 11/27/06, Nikolai Weibull <now@xxxxxxxx> wrote:
> On 11/27/06, Wayne Davison <wayned@xxxxxxxxxxxxxxxxxxxxx> wrote:
> > On Sat, Nov 25, 2006 at 06:52:50PM +0100, Nikolai Weibull wrote:
> > > Yes, but that I already have.  The -D information somehow isn't
> > > recorded.  I thought it was incappendhistory that caused this, but I
> > > don't have that set.
> >
> > The SHARE_HISTORY option also causes this.  This is because the current
> > algorithm for sharing history writes out the history lines as soon as
> > you enter the command.  Perhaps we should revisit the reasons for this
> > design choice to see if we still agree that this is the best spot to do
> > the shared/inc-append history updating.
>
> I don't have that set either.  dang...
>
> setopt autocd                                 \
>        autopushd                              \
>        completeinword nolistambiguous         \
>        rcexpandparam rcquotes                 \
>        correct dvorak                         \
>        nonotify                               \
>        nobeep


Oh boy.  Turns out extendedhistory wasn't on by default like I
thought.  Anyway, even with it set it doesn't work.  Can appendhistory
mess it up?

Also, why isn't histsavebycopy set by default, as the documentation
suggests that it be set unless you have special needs?

 nikolai