From: "Smarasderagd" <smarry@vex.net>
To: rc@hawkwind.utcs.toronto.edu, schwartz@bio.cse.psu.edu
Subject: Re: builtins
Date: Fri, 12 May 2000 01:49:08 -0400 [thread overview]
Message-ID: <20000512054908.23614.qmail@pantransit.reptiles.org> (raw)
Scott Schwartz <schwartz@bio.cse.psu.edu> writes:
>My $0.02: if you have echo as a builtin, read deserves the same.
Should it honour escaped newlines the way Bourne shell read does?
Wouldn't it be nice if you could read arrays? But what we really
want is to generalize all of the hidden goo that reads input until
we can reimplement the main loop as "while () {read a; eval $a}", and
optionally also "echo $a >> $history", and a replacement for - and --
that lets you do structural editing...
>My other $0.02: echo needs a sibling builtin, quote, to enquote it's
>arguments so that they can be read by the shell. Lisp got that right ages
>ago. Inferno got it right more recently.
Oh, I guess that IS where you want to go. :)
Seriously, I don't see any real reason why a quoting function doesn't
make sense, since whatis already does this...
next reply other threads:[~2000-05-14 5:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-12 5:49 Smarasderagd [this message]
[not found] <tell@cs.unc.edu>
2000-05-08 23:25 ` building rc on QNX4 Stephen Tell
2000-05-10 0:37 ` builtins Scott Schwartz
2000-05-12 7:22 ` builtins Carlo Strozzi
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=20000512054908.23614.qmail@pantransit.reptiles.org \
--to=smarry@vex.net \
--cc=rc@hawkwind.utcs.toronto.edu \
--cc=schwartz@bio.cse.psu.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.
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).