From: Parker Ellertson <pellertson@firemail.cc>
To: 9fans@9fans.net
Subject: Re: [9fans] Rc Recursion
Date: Fri, 25 Jan 2019 20:35:28 -0700 [thread overview]
Message-ID: <30a10d76-b727-9d4c-6ba6-b7ce1fa632e6@firemail.cc> (raw)
In-Reply-To: <CAJSxfmKDRf-VVoQPahXXZRjOq_x_W4e0U-xmDk9sM7peir5x5Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 694 bytes --]
sweet! thanks
On 1/25/19 8:03 PM, Skip Tavakkolian wrote:
> recursion works fine. here's an example:
>
> https://gist.github.com/9nut/476be37e25e9561f525036bcf60a2014
>
>
> On Fri, Jan 25, 2019 at 6:37 PM Parker Ellertson
> <pellertson@firemail.cc> wrote:
>
> This might be a stupid question to ask, but how well does the rc shell
> support recursion in its scripts? I ask because I'm writing a script
> which will rely on calling itself a whole bunch. I could write it in
> python or go or some other language, but I've been wanting to give rc a
> try for a while. Seems like a cool shell to write scripts in. Any info
> is appreciated!
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 673 bytes --]
prev parent reply other threads:[~2019-01-26 3:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 2:36 Parker Ellertson
2019-01-26 3:03 ` Skip Tavakkolian
2019-01-26 3:35 ` Parker Ellertson [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=30a10d76-b727-9d4c-6ba6-b7ce1fa632e6@firemail.cc \
--to=pellertson@firemail.cc \
--cc=9fans@9fans.net \
/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.
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).