zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: Zsh workers <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: 3.1.6-dev-18 AIX dependency fixes
Date: Sun, 13 Feb 2000 18:43:06 +0000	[thread overview]
Message-ID: <E12K3vj-0001rZ-00.2000-02-13-18-39-36@mail4.svr.pol.co.uk> (raw)
In-Reply-To: "Oliver Kiddle"'s message of "Sat, 12 Feb 2000 16:47:22 GMT." <38A58E9A.8ECEE26D@u.genie.co.uk>

Oliver Kiddle wrote:
> Just mod_exports added.

There was a line wrapping problem again, so this had to be applied by hand.

> Are we going to get a 3.1.7 (and maybe 4.0) out soonish? The 3.1 series
> seems to be quite stable to me now. Also, 3.0 seems to be very far
> behind now and it might be better to have more users using the new
> functionality.

3.1.7 should certainly appear soon.  The major items on my to-do list are

-- rewrite compinstall.  Either this has to be done or it should simply be
missed out, since the current version is essentially useless.  I have
started working on this, but there is a lot to do even to be able to set
the basic styles for basic contexts.  In addition it's aimed at a moving
target, even if moving more slowly.

-- I'd like to get out the chapter of my zsh guide for new-style completion
in time for the release.  The first draft is more or less finished, though
the same problems apply and it needs rewriting already (I've changed the
context stuff, but it still needs checking, and I need to change the
$compmatchers stuff).

Neither of these is absolutely required, but if I don't get them ready for
3.1.7 they are likely to drift off.

There are other things --- for example, I suspect getting and setting of
parameters internally needs a complete rethink --- but it's unrealistic to
put a timetable on them.

Since completion now appears to be pretty much stable, 4.0.1 could then
appear without too many user-visible changes.  However, I think the
wordcode stuff is going to continue to evolve anyway (rewrite parser to
eliminate the old-style structs altogether, aim to eliminate
HEAPALLOC/PERMALLOC by passing allocation strategy directly to appropriate
constructors), and I don't think it would be a good idea to produce 4.0.1
with the current hybrid state, though it won't matter for 3.1.7.

-- 
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>


  parent reply	other threads:[~2000-02-13 18:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-12 16:47 Oliver Kiddle
2000-02-12 18:13 ` Next release (Re: PATCH: 3.1.6-dev-18 AIX dependency fixes) Bart Schaefer
2000-02-13 18:43 ` Peter Stephenson [this message]
2000-02-14  9:44 PATCH: 3.1.6-dev-18 AIX dependency fixes Sven Wischnowsky

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=E12K3vj-0001rZ-00.2000-02-13-18-39-36@mail4.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).