Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Remove history entries
- X-seq: zsh-workers 25894
- From: Peter Stephenson <pws@xxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: Remove history entries
- Date: Tue, 14 Oct 2008 13:07:19 +0100
- In-reply-to: <2d460de70810140448h5a47e48aw103779f180f8e84b@xxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <slrngf4oua.r2h.joerg@xxxxxxxxxxxx> <2d460de70810140426t7c382888pfc22e02c17396d55@xxxxxxxxxxxxxx> <20081014124351.2047fb30@news01> <2d460de70810140448h5a47e48aw103779f180f8e84b@xxxxxxxxxxxxxx>
"Richard Hartmann" wrote:
> On Tue, Oct 14, 2008 at 13:43, Peter Stephenson <pws@xxxxxxx> wrote:
>
> > It might be possible to force it to overwrite it, but I don't think that's
> > a simple change.
>
> Can't you "just" move the hooks for these functions? And/or introduce
> a new set?
No, the hook has to run before the line is saved. Delaying saving it
until other code has run breaks the current model for how history code
works. In particular executing history commands within the executed but
unsaved command would be screwed up. There may be a fix, but I don't
see an easy fix.
--
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