Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Extending zsh capabilities
- X-seq: zsh-workers 4253
- From: Bruce Stephens <b.stephens@xxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: Extending zsh capabilities
- Date: 27 Jul 1998 12:18:16 +0100
- In-reply-to: Mark Hessling's message of "Mon, 27 Jul 1998 20:07:23 +1000 (EST)"
- References: <Pine.OSF.3.92.980727195209.20094B-100000@xxxxxxxxxxxxxxxxx>
- Sender: B.Stephens@xxxxxxxxx
Mark Hessling <m.hessling@xxxxxxxxxx> writes:
> Executing a Rexx program within a current process is straighforward,
> I need to call the API function RexxStart() with the filename as one
> of the arguments. The interface is simple; its knowing where to
> hook it into zsh that is my biggest problem.
[caveat: I don't know much about zsh internals]
A first thought is to look at where the shell executes external
commands, and fiddle there. But as you comment, that's in the wrong
process. There're presumably lots of subtleties to do with io
redirection, interruptability and things, so looking at builtins is
probably better.
How about, as a first cut, writing a builtin "rexx" which would
execute a Rexx script? That could be done as a module (like stat).
I'd have thought that would be acceptable in usage too: you'd just
create aliases for Rexx scripts you used a lot. If not, you could
change the unknown function so it would try executing an unknown
command as a Rexx script, or work a bit harder.
Probably Zefram has better ideas; I'm sure he was threatening to do
the same for Perl.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author