From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: 4.3.4-dev-3
Date: Mon, 26 Nov 2007 16:05:45 +0000 [thread overview]
Message-ID: <11115.1196093145@csr.com> (raw)
Another test builds before 4.3.5 is at
ftp://ftp.zsh.org/development/zsh-4.3.4-dev-3.tar.gz
Various problems turned up.
- Rework curses headers
- Attempt to fix warnings on Tru64 (unverified)
- Memory management with environment strings
- Fix for prompt lengths
- zshcalsys.1 manual was missing
- Memory management of termcap strings
Still haven't updated NEWS etc., sorry.
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
next reply other threads:[~2007-11-26 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 16:05 Peter Stephenson [this message]
2007-11-26 19:13 ` 4.3.4-dev-3 Matt Wozniski
2007-11-26 19:27 4.3.4-dev-3 Ryan F
2007-11-26 23:47 ` 4.3.4-dev-3 Peter Stephenson
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=11115.1196093145@csr.com \
--to=pws@csr.com \
--cc=zsh-workers@sunsite.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).