From: Byron Rakitzis <byron>
To: rc, rsalz@bbn.com
Subject: Re: variables in ~ patternlists?
Date: Fri, 18 Oct 1991 15:18:03 -0500 [thread overview]
Message-ID: <91Oct18.151804cdt.18991@archone.tamu.edu> (raw)
This is not how patterns work in rc; The only way to get
* to match any characters is for it to appear LITERALLY
and UNQUOTED. Therefore, only
~ foo.c *
will match, not
bar='*.c'
~ foo.c $bar
The only way to get around this is with an explicit eval
statement:
eval ~ $1 $foo
will present $foo to rc as if it had been rescanned (which
it is, actually).
I find these quoting rules to be quite simple, actually. Duff
explains them quite well in the paper bundled with rc-1.2.
next reply other threads:[~1991-10-18 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-10-18 20:18 Byron Rakitzis [this message]
-- strict thread matches above, loose matches on Subject: below --
1991-10-18 20:27 Rich Salz
1991-10-18 20:05 Rich Salz
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=91Oct18.151804cdt.18991@archone.tamu.edu \
--to=rsalz@bbn.com \
/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).