From: Sam <sah@softcardsystems.com>
To: 9fans mailing list <9fans@cse.psu.edu>
Subject: Re: [9fans] Ugly hack
Date: Sat, 15 Feb 2003 11:18:41 -0500 [thread overview]
Message-ID: <Pine.LNX.4.30.0302151105570.14996-100000@athena> (raw)
In-Reply-To: <20030215174605.I9084@cackle.proxima.alt.za>
Would I were bothered by this, I'ld be more inclined
towards:
fn cdd { for(i) { if(test -d $i){ cd $i } } }
Note there's a bug in this approach due to rc's
for lacking a break equivalent, but it's unlikely
to bite.
Always better to use the tools than hack them if at all
possible.
Cheers,
Sam
next prev parent reply other threads:[~2003-02-15 16:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-15 15:46 Lucio De Re
2003-02-15 16:18 ` Sam [this message]
2003-02-15 16:21 ` Dan Cross
2003-02-15 16:29 ` Lucio De Re
2003-02-15 23:56 ` Geoff Collyer
2003-02-16 9:20 ` Lucio De Re
2003-02-16 9:25 ` Lucio De Re
2003-02-16 12:18 ` Lucio De Re
2003-02-16 12:45 ` Lucio De Re
2003-02-16 14:19 ` Russ Cox
2003-02-16 15:00 ` Lucio De Re
2003-02-16 15:31 ` David Butler
2003-02-16 15:40 ` Russ Cox
2003-02-17 5:27 ` Lucio De Re
2003-02-17 9:53 ` John Kodis
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=Pine.LNX.4.30.0302151105570.14996-100000@athena \
--to=sah@softcardsystems.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).