From: "Zefram" <zefram@tao.co.uk>
To: m.hessling@qut.edu.au (Mark Hessling)
Cc: zsh-workers@math.gatech.edu
Subject: Re: Extending zsh capabilities
Date: Thu, 30 Jul 1998 09:04:48 +0100 (BST) [thread overview]
Message-ID: <199807300804.JAA14931@diamond.tao.co.uk> (raw)
In-Reply-To: <Pine.OSF.3.92.980730085244.2150A-100000@pigeon.qut.edu.au> from "Mark Hessling" at Jul 30, 98 08:59:43 am
Mark Hessling wrote:
>I downloaded zsh 3.1.3 and am attempting to build it. Unfortunately I
>am having problems
There were some bugs in the build process in 3.1.3. These are fixed
in 3.1.4.
-zefram
next prev parent reply other threads:[~1998-07-30 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199807270524.BAA22704@math.gatech.edu>
1998-07-27 10:07 ` Mark Hessling
1998-07-27 11:18 ` Bruce Stephens
1998-07-27 12:13 ` Peter Stephenson
1998-07-29 22:59 ` Mark Hessling
1998-07-30 8:04 ` Zefram [this message]
1998-07-30 8:15 ` 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=199807300804.JAA14931@diamond.tao.co.uk \
--to=zefram@tao.co.uk \
--cc=m.hessling@qut.edu.au \
--cc=zsh-workers@math.gatech.edu \
/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).