From: Matt <matt@proweb.co.uk>
To: 9fans <9fans@cse.psu.edu>
Cc: rc@hawkwind.utcs.utoronto.ca
Subject: unix RC shell bug
Date: Sat, 1 Sep 2001 00:11:16 -0500 [thread overview]
Message-ID: <7126271516.20010901051116@proweb.co.uk> (raw)
In-Reply-To: <E15cuG8-000P4t-0Y@anchor-post-34.mail.demon.net>
after hours of not noticing one of my variables was a list and not a
string (it's 5am I've been on this since 10pm!) I eventually got to
this sorry state.
in good ol' plan9
cpu% t=(1 2 3 6 7)
cpu% echo $#t
5
cpu% echo $"t
1 2 3 6 7
in /usr/local/bin/rc (ver 1.6) on FreeBSD (ver 4.2-RELEASE)
; t=(1 2 3 6 7)
; echo $#t
5
; echo $"t
syntax error
just fyi
next parent reply other threads:[~2001-09-03 5:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E15cuG8-000P4t-0Y@anchor-post-34.mail.demon.net>
2001-09-01 5:11 ` Matt [this message]
2001-09-03 6:14 ` Callum Gibson
2001-09-03 6:18 ` Decklin Foster
2001-09-03 7:23 Byron Rakitzis
2001-09-03 8:19 Smarasderagd
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=7126271516.20010901051116@proweb.co.uk \
--to=matt@proweb.co.uk \
--cc=9fans@cse.psu.edu \
--cc=rc@hawkwind.utcs.utoronto.ca \
/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).