zsh-workers
 help / color / mirror / code / Atom feed
From: Bruce Stephens <b.stephens@isode.com>
To: zsh-workers@math.gatech.edu
Subject: Re: Extending zsh capabilities
Date: 27 Jul 1998 12:18:16 +0100	[thread overview]
Message-ID: <vbg1fnk0ef.fsf@snake.isode.com> (raw)
In-Reply-To: Mark Hessling's message of "Mon, 27 Jul 1998 20:07:23 +1000 (EST)"

Mark Hessling <m.hessling@qut.edu.au> 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.


  reply	other threads:[~1998-07-27 11:23 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 [this message]
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

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=vbg1fnk0ef.fsf@snake.isode.com \
    --to=b.stephens@isode.com \
    --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).