rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Byron Rakitzis <byron@rakitzis.com>
To: bengt@softwell.se, rc@hawkwind.utcs.toronto.edu
Subject: Re: what if?, suggestion to re-instate the alternative if not syntax...
Date: Thu, 9 Dec 1999 03:13:04 -0500	[thread overview]
Message-ID: <199912090813.AAA23378@peanut.rakitzis.com> (raw)

>I ahve a very rare wish to run Plan9 rc scripts using Byrons rc.

Without looking at the source, you'd have to change two things: the
yacc file (and the lexer), and any "undumping" code to emit function
definitions for export. The change should be trivial in both cases.

The question I have is why you'd want to do this!? Are there any useful
"standalone" rc scripts which are portable between plan9 and unix?

             reply	other threads:[~1999-12-09  9:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-09  8:13 Byron Rakitzis [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-12-10  9:06 Bengt Kleberg
1999-12-10  9:00 Bengt Kleberg
1999-12-08 15:13 Bengt Kleberg
1999-12-09  8:00 ` Decklin Foster
1999-12-09  8:22   ` Markus Friedl

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199912090813.AAA23378@peanut.rakitzis.com \
    --to=byron@rakitzis.com \
    --cc=bengt@softwell.se \
    --cc=rc@hawkwind.utcs.toronto.edu \
    --subject='Re: what if?, suggestion to re-instate the alternative if not syntax...' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).