From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] slight glossing over 8) ?
Date: Tue, 12 Nov 2002 13:30:16 -0500 [thread overview]
Message-ID: <64936f1fb379061975d9674bb652ee4f@plan9.bell-labs.com> (raw)
oh, right. you know, you don't really need any quotes.
two quotes is the same as none.
that is,
/usr/matt/bin/web_plumber -w tcp!192.168.1.101!8005 ''$0''
is like
x=''
/usr/matt/bin/web_plumber -w tcp!192.168.1.101!8005 $x$0$x
while this
window webbrowser ''''$0''''
is like
x=''''
window webbrowser $x$0$x
next reply other threads:[~2002-11-12 18:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 18:30 Russ Cox [this message]
2002-11-12 18:50 ` matt
-- strict thread matches above, loose matches on Subject: below --
2002-11-12 19:21 Russ Cox
2002-11-14 23:04 ` matt
2002-11-14 23:07 ` andrey mirtchovski
2002-11-12 17:02 Russ Cox
2002-11-12 18:21 ` matt
2002-11-12 16:03 rob pike, esq.
2002-11-12 2:40 Russ Cox
2002-11-12 12:15 ` matt
2002-11-12 0:58 matt
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=64936f1fb379061975d9674bb652ee4f@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@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).