From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: Two more wordcode problems, probably
Date: Thu, 20 Jan 2000 20:01:37 +0000 [thread overview]
Message-ID: <E12BNiG-0002yg-00.2000-01-20-19-57-48@cmailg5.svr.pol.co.uk> (raw)
In-Reply-To: "Peter Stephenson"'s message of "Thu, 20 Jan 2000 19:57:03 GMT." <E12BNdm-0000e9-00.2000-01-20-19-53-10@mail4.svr.pol.co.uk>
Peter Stephenson wrote:
> These are presumably both a result of the wordcode changes:
By the way, I've been delaying 3.1.6-dev-16 (just for a few days, probably)
to get something with Sven's new wordcode which isn't going to cause too
much hassle for all and sundry. I can't see a good reason for keeping it
back, this is what beta versions are for.
--
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
prev parent reply other threads:[~2000-01-20 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-20 19:57 Peter Stephenson
2000-01-20 19:59 ` Chmouel Boudjnah
2000-01-20 20:01 ` Peter Stephenson [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=E12BNiG-0002yg-00.2000-01-20-19-57-48@cmailg5.svr.pol.co.uk \
--to=pws@pwstephenson.fsnet.co.uk \
--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).