From: Alan Watson <alan@oldp.astro.wisc.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: bug in ~ ?
Date: Wed, 26 May 1993 20:44:15 -0400 [thread overview]
Message-ID: <9305270044.AA17386@oldp.astro.wisc.edu> (raw)
; foo=()
; ~ $foo () bar && echo yes [a]
; ~ $foo () && echo yes [b]
yes
; ~ () () && echo yes [c]
yes
; foo=foo
; ~ $foo foo bar && echo yes [d]
yes
Question: why doesn't [a] echo yes?
This is what I think is going on: rc normally takes the arguments to a
command and makes them into a list, in the process of which any null
lists are eliminated. While this the behaviour one normally wants, it
doesn't seem right here.
rc doesn't seem to amalgamate the first argument of ~ with the rest (from my
reading of the grammar), so it is already a special case.
next reply other threads:[~1993-05-27 0:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-05-27 0:44 Alan Watson [this message]
1993-05-27 4:53 Byron Rakitzis
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=9305270044.AA17386@oldp.astro.wisc.edu \
--to=alan@oldp.astro.wisc.edu \
--cc=rc@hawkwind.utcs.toronto.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).