From: Peter Stephenson <pws@ifh.de>
To: zsh-workers@math.gatech.edu (Zsh hackers list),
Mark Hessling <m.hessling@qut.edu.au>
Subject: Re: Extending zsh capabilities
Date: Thu, 30 Jul 1998 10:15:54 +0200 [thread overview]
Message-ID: <199807300815.KAA21966@hydra.ifh.de> (raw)
In-Reply-To: "Mark Hessling"'s message of "Thu, 30 Jul 1998 08:59:43 MST." <Pine.OSF.3.92.980730085244.2150A-100000@pigeon.qut.edu.au>
Mark Hessling wrote:
> I downloaded zsh 3.1.3 and am attempting to build it. Unfortunately I
> am having problems :-(
These are intrinsic to 3.1.3, unless you are running a sh which is
actually zsh in disguise. 3.1.4 should be around on the official archives
and has this fixed.
I realised my trick of aliasing /* probably doesn't work for complex
Rexx scripts, because zsh tries to parse the whole thing first and runs
into incompatible syntax. I then thought of doing something with
preexec, but I now think that's too limited. Of course, if you know in
advance that something is a Rexx script, there are all sorts of things you
can do, but I can't offhand think of a really good way when you don't.
(Even my /* way implies you had already sorted Rexx scripts into function
directories, and if you do that, you might as well have a special directory
and use some code in .zshrc to alias foo="rexx $rexxpath/foo"
or whatever.)
--
Peter Stephenson <pws@ifh.de> Tel: +39 50 844536
WWW: http://www.ifh.de/~pws/
Gruppo Teorico, Dipartimento di Fisica
Piazza Torricelli 2, 56100 Pisa, Italy
prev parent reply other threads:[~1998-07-30 8:35 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
1998-07-30 8:15 ` 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=199807300815.KAA21966@hydra.ifh.de \
--to=pws@ifh.de \
--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).