From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: updating context on Ubuntu 6.06
Date: Wed, 26 Jul 2006 22:34:07 +0200 [thread overview]
Message-ID: <44C7D1BF.1040608@elvenkind.com> (raw)
In-Reply-To: <E1G5pLm-0005HT-00@skye.ra.phy.cam.ac.uk>
Sanjoy Mahajan wrote:
>
> It was hard to find a machine not running bash, a measure of the
> success of free software. But I eventually found a nearby Solaris
> machine running 'sh' (couldn't tell which version), but it's man entry
> says the same:
>
> if $@ is within a pair of double quotes, the positional
> parameters are substituted and quoted, separated by unquoted
> spaces ("$1""$2" ... )
>
> So I think it's safe, and increases robustness, to change $@ -> "$@"
> in all the stub scripts.
Many thanks for looking that up.
>
> One question: How safe is it that the ctxtools.rb script is
> overwritten by the unzip in the middle of running the script? Will
> ruby execute half from the old script and half from the new script?
That is safe. Modern scripting languages normally byte-compile the
entire file before running it (the main advantage is that this
captures syntrax errors before any real harm is done).
Taco
next prev parent reply other threads:[~2006-07-26 20:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 20:24 Sanjoy Mahajan
2006-07-26 8:36 ` Ralf Schmitt
2006-07-26 9:36 ` Taco Hoekwater
2006-07-26 10:36 ` Jano Kula
2006-07-26 11:20 ` Ralf Schmitt
2006-07-26 15:17 ` Sanjoy Mahajan
2006-07-26 16:13 ` Taco Hoekwater
2006-07-26 19:47 ` Sanjoy Mahajan
2006-07-26 20:34 ` Taco Hoekwater [this message]
2006-07-26 20:57 ` Hans Hagen
2006-07-26 21:01 ` Hans Hagen
2006-07-26 21:29 ` Switching Font Size in a Natural Table Neal Lester
2006-08-01 23:31 ` Mojca Miklavec
2006-07-26 22:10 ` updating context on Ubuntu 6.06 Sanjoy Mahajan
2006-07-27 8:05 ` Hans Hagen
2006-07-27 8:46 ` Taco Hoekwater
2006-07-27 8:04 ` Hans Hagen
2006-07-27 12:37 ` Sanjoy Mahajan
2006-07-26 21:02 ` Hans Hagen
2006-07-26 14:43 ` Sanjoy Mahajan
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=44C7D1BF.1040608@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.nl \
/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).