zsh-workers
 help / color / mirror / code / Atom feed
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: Fri, 4 Jun 1999 04:38:43 +0000	[thread overview]
Message-ID: <990604043844.ZM4317@candle.brasslantern.com> (raw)
In-Reply-To: <Pine.GSO.4.10.9906031943490.11008-100000@house.clari.net>

On Jun 3,  8:11pm, Wayne Davison wrote:
} Subject: Re: PATCH: 3.0.6-pre-3: mainly history bug fixes
}
} 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)
} 
} Quite correct, I did not include that change, nor any history change
} that was not a bug fix or a code optimization.

Thank you (both for doing it and reassuring me about it).

} > 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.

Aha.

} 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?

I'm thinking about it ... of course one hopes that there won't be any
reason to go backwards ... it's impossible to make such a change in a
forwards-compatible way (such that the old version won't be confused)
so there's no point in doing more than you have; the question is if the
change should be made at all.

Here's a thought that just occurred to me:  What if we have 3.0.6 keep
writing hist files in the old format, but treat a finish time less than
the start time as the new format?  Then 3.0.6 and 3.1.6 will be able to
exchange history files with each other.  A transition phase like that
seems worthwhile to me.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


      reply	other threads:[~1999-06-04  4:39 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
1999-06-04  4:38     ` Bart Schaefer [this message]

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=990604043844.ZM4317@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).