From: Noah Evans <noah.evans@cwru.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] multiple inputs
Date: Thu, 1 Apr 2004 13:02:48 -0500 [thread overview]
Message-ID: <a09573d164acccba208e5036b39f0381@cwru.edu> (raw)
In-Reply-To: <94ec8e21ec12b4dc3ae41b46df9420b8@vitanuova.com>
[-- Attachment #1: Type: text/plain, Size: 180 bytes --]
:)
Exactly, But I love code that writes itself so I have a hard time giving it up ;) hence the interest in playing with the parse tree.
Thanks for your insights,
Noah
[-- Attachment #2: Type: message/rfc822, Size: 3046 bytes --]
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] multiple inputs
Date: Thu, 01 Apr 2004 20:47:56 +0100
Message-ID: <94ec8e21ec12b4dc3ae41b46df9420b8@vitanuova.com>
> a way to make the shell less dangerous when it expands metacharacters
it's easy... don't use eval! (i've written loads of rc scripts and i
don't think i've ever used eval).
if you really wanted to use eval in a safe way, you'd need some
support for quoting; for instance:
% quote a 'b c' d
a 'b c' d
%
but it'd be awkward to use this in rc due to the `{} $ifs splitting.
i made this kind of thing easier to do in the inferno shell, but i'm
still not that convinced - it's very easy to build up inpenetrable
layers.
next prev parent reply other threads:[~2004-04-01 18:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 6:53 npe
2004-03-30 8:22 ` matt
2004-03-30 11:48 ` glenda
2004-03-30 14:03 ` matt
2004-03-30 12:10 ` glenda
2004-03-30 16:07 ` rog
2004-03-30 14:15 ` Noah Evans
2004-03-30 16:25 ` rog
2004-03-30 16:14 ` Noah Evans
2004-03-30 18:27 ` rog
2004-03-30 16:28 ` Noah Evans
2004-03-31 20:22 ` boyd, rounin
2004-04-01 13:01 ` Noah Evans
2004-04-01 15:31 ` rog
2004-04-01 14:43 ` boyd, rounin
2004-04-01 16:26 ` Russ Cox
2004-04-01 17:36 ` rog
2004-04-01 15:58 ` Noah Evans
2004-04-01 18:42 ` rog
2004-04-01 17:34 ` Noah Evans
2004-04-01 19:47 ` rog
2004-04-01 18:02 ` Noah Evans [this message]
2004-04-02 1:48 ` Geoff Collyer
2004-04-01 20:04 ` David Tolpin
2004-04-02 1:46 ` Geoff Collyer
2004-04-02 2:09 Noah Evans
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=a09573d164acccba208e5036b39f0381@cwru.edu \
--to=noah.evans@cwru.edu \
--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).