Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Why does extended_history timestamp commands that are not under its 'control'?
- X-seq: zsh-users 13070
- From: Peter Stephenson <pws@xxxxxxx>
- To: "Zsh users list" <zsh-users@xxxxxxxxxx>
- Subject: Re: Why does extended_history timestamp commands that are not under its 'control'?
- Date: Mon, 28 Jul 2008 12:36:54 +0100
- In-reply-to: <2d460de70807280429u1ac6e0e1v68e5f81f5a7a753@xxxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <2d460de70807280429u1ac6e0e1v68e5f81f5a7a753@xxxxxxxxxxxxxx>
"Richard Hartmann" wrote:
> when you setopt extended_history, ZSH will put the timestamp of when it
> exits in front of all commands that have not been timestamped, yet.
> I can see why this could be considered useful, but personally, I dislike
> this behaviour. If exact information when a command was issued is not
> available, I would rather not store this information at all. Is there a
> way to make ZSH not touch those entries?
"Not storing" and "not touching" the information are different things:
if it's not touched when written, it's simply stored as gibberish. It
sounds like what you're asking for is an extra flag or a slightly
different variant of the format.
--
Peter Stephenson <pws@xxxxxxx> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
Messages sorted by:
Reverse Date,
Date,
Thread,
Author