Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

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

X-seq: zsh-users 11044
From: Wayne Davison <wayned@xxxxxxxxxxxxxxxxxxxxx>
To: Nikolai Weibull <now@xxxxxxxx>
Subject: Re: What was the reason for history -D not reporting runtimes?
Date: Mon, 27 Nov 2006 10:08:42 -0800
Cc: zsh-users@xxxxxxxxxx
In-reply-to: <dbfc82860611270846wa3924a7i65d54ef9ca309fb7@xxxxxxxxxxxxxx>
Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
References: <dbfc82860611240516w403e14fes7ef5a8d29148512c@xxxxxxxxxxxxxx> <17393e3e0611250841v6a5e3d73ha185b3f3b44509b9@xxxxxxxxxxxxxx> <dbfc82860611250952w68b615ebl250e3d8ede444739@xxxxxxxxxxxxxx> <20061127143109.GA26291@xxxxxxxxx> <dbfc82860611270814p115da7afu3c8ada7795a03701@xxxxxxxxxxxxxx> <dbfc82860611270846wa3924a7i65d54ef9ca309fb7@xxxxxxxxxxxxxx>

On Mon, Nov 27, 2006 at 05:46:25PM +0100, Nikolai Weibull wrote:
> Also, why isn't histsavebycopy set by default, as the documentation
> suggests that it be set unless you have special needs?

It is set by default in a zsh that supports the option.  If I run
"unsetopt | fgrep copy", I see "nohistsavebycopy", which means that
the option is enabled (i.e. that "unsetopt nohistsavebycopy" is what
is currently in effect, and thus the double-negation of that command,
"setopt histsavebycopy", is also in effect).

..wayne..

References:
- What was the reason for history -D not reporting runtimes?
  - From: Nikolai Weibull
- Re: What was the reason for history -D not reporting runtimes?
  - From: Nikolai Weibull
- Re: What was the reason for history -D not reporting runtimes?
  - From: Wayne Davison
- Re: What was the reason for history -D not reporting runtimes?
  - From: Nikolai Weibull
- Re: What was the reason for history -D not reporting runtimes?
  - From: Nikolai Weibull

Messages sorted by: Reverse Date, Date, Thread, Author