From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Wayne Davison <wayne@clari.net>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: 3.0.6-pre-3: mainly history bug fixes
Date: Thu, 3 Jun 1999 06:19:22 +0000 [thread overview]
Message-ID: <990603061922.ZM2764@candle.brasslantern.com> (raw)
In-Reply-To: <199906020955.CAA04266@bebop.clari.net>
On Jun 2, 2:55am, Wayne Davison wrote:
} Subject: PATCH: 3.0.6-pre-3: mainly history bug fixes
}
} I believe I've managed to distill most of the bug fixes that were
} included in my previous history changes into a separate patch for
} 3.0.6. I haven't had much of a chance to test this yet, but since
} most of this is lifted from my previous changes, it should be OK.
}
} Most of these changes were originally lifted from the 3.1.x source.
Pardon my paranoia, but ...
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.
} One non-bugfix that is included here is the change I made to the
} EXTENDED_HISTORY output format where it writes the finish time in
} elapsed seconds instead of epoch seconds -- I figured if this is
} going to change in 3.1.x, we might as well get it going in 3.0.6 too.
I hadn't thought much about this before, but what's going to happen when
somebody with this option set fires up a new zsh and it loads his existing
old-format .zhistory? All the timestamps are going to look like garbage,
aren't they?
Seems to me that a change like this should be written in different syntax,
so that there's no chance of confusing the old numbers for the new.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-06-03 6:37 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 [this message]
1999-06-04 3:11 ` Wayne Davison
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=990603061922.ZM2764@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=wayne@clari.net \
--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).