Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: revisiting history-file rewriting
- X-seq: zsh-workers 21016
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: revisiting history-file rewriting
- Date: Fri, 18 Mar 2005 21:15:37 +0000
- In-reply-to: <20050318181921.GF5500@xxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20050316204059.GA1298@xxxxxxxxx> <1050317180338.ZM32687@xxxxxxxxxxxxxxxxxxxxxxx> <20050318181921.GF5500@xxxxxxxxx>
On Mar 18, 10:19am, Wayne Davison wrote:
} Subject: Re: revisiting history-file rewriting
}
} I don't like OVERWRITE_HISTORY because it sounds like something that
} conflicts with APPEND_HISTORY. Perhaps my option name needs to be
} improved -- how about HIST_WRITE_IN_PLACE?
That name seems a bit unwieldy, but I suppose one won't be typing it all
that often.
Appending to the history writes in place, too, though, doesn't it? Or
at least incremental appending does?
Maybe HIST_SAVE_BY_COPY, defaulting to on?
Another random thought, far too late for its own good:
HIST_SAVE_NO_DUPS default off should have been HIST_SAVE_DUPS default on,
so as to avoid the double negative in NO_HIST_SAVE_NO_DUPS. Oh, well.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author