From: Wayne Davison <wayne@clari.net>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: 3.0.6-pre-3: mainly history bug fixes
Date: Thu, 3 Jun 1999 20:11:57 -0700 (PDT) [thread overview]
Message-ID: <Pine.GSO.4.10.9906031943490.11008-100000@house.clari.net> (raw)
In-Reply-To: <990603061922.ZM2764@candle.brasslantern.com>
On Thu, 3 Jun 1999, Bart Schaefer wrote:
> Something I don't want to accidentally do is fold in the history
> search change (whole words at beginning of line) that caused so
> much complaint and eventual back-patching. I don't *think* I see
> it in here anywhere, but if you can reassure me, please do.
Quite correct, I did not include that change, nor any history change
that was not a bug fix or a code optimization. For example, several
functions now properly use the numeric prefix that had previously
ignored it. Also, the majority of the differences in zle_hist.c was
from a unification of the upline/downline code into separate
functions so that the formerly-duplicated code would not continue to
diverge (it was inconsistent in one case, I believe).
> what's going to happen when somebody with this option set fires up
> a new zsh and it loads his existing old-format .zhistory?
The new code is smart enough to treat a finish length that is >= the
start time as the old format. This should be OK, since I don't
believe that people will be running a program continuously for over
29 years.
Going back from a new shell with this new EXTENDED_HISTORY format to
an old shell without it can cause the finish times to read in as
very early dates, but I wasn't particularly concerned about this.
Do you feel differently?
..wayne..
next prev parent reply other threads:[~1999-06-04 3:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-02 9:55 Wayne Davison
1999-06-03 6:19 ` Bart Schaefer
1999-06-04 3:11 ` Wayne Davison [this message]
1999-06-04 4:38 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.10.9906031943490.11008-100000@house.clari.net \
--to=wayne@clari.net \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).