rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Alan Watson <alan@oldp.astro.wisc.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: Need help with input loop (long)
Date: Wed, 15 Sep 1993 14:52:03 -0400	[thread overview]
Message-ID: <9309151852.AA26050@oldp.astro.wisc.edu> (raw)

> fn read {
>   $1=`{/usr/bin/line; if(! ~ $status 0) return 1}
> }

I believe your attempt to return from a command substitution within a
function is causing rc to get thoroughly confused.  I must admit that I
can't decide whether to be appalled or impressed by your novel use of
this construct!

Getting read right it tricky.  I recommend the read command in the FAQ
(although make sure you have $nl defined -- fixed in the next


             reply	other threads:[~1993-09-15 18:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-09-15 18:52 Alan Watson [this message]
  -- strict thread matches above, loose matches on Subject: below --
1993-09-15 17:37 carvell

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=9309151852.AA26050@oldp.astro.wisc.edu \
    --to=alan@oldp.astro.wisc.edu \
    --cc=rc@hawkwind.utcs.toronto.edu \


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