From: Parker Ellertson <pellertson@firemail.cc>
To: 9fans@9fans.net
Subject: [9fans] Rc Recursion
Date: Fri, 25 Jan 2019 19:36:29 -0700 [thread overview]
Message-ID: <7dcd30a9-de54-0958-b806-29373375ce55@firemail.cc> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 499 bytes --]
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!
--
Parker Ellertson
================
email: pellertson@firemail.cc
pgp public key attached for those
who care
[-- Attachment #1.1.2: 0xF7B8433D74D6F2DB.asc --]
[-- Type: application/pgp-keys, Size: 2505 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 673 bytes --]
next reply other threads:[~2019-01-26 2:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 2:36 Parker Ellertson [this message]
2019-01-26 3:03 ` Skip Tavakkolian
2019-01-26 3:35 ` Parker Ellertson
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=7dcd30a9-de54-0958-b806-29373375ce55@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).