From: William Josephson <jkw@eecs.harvard.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] OT: plan9port question
Date: Sun, 6 Mar 2005 14:14:11 -0500 [thread overview]
Message-ID: <20050306191411.GA75074@mero.morphisms.net> (raw)
In-Reply-To: <00e201c5227d$e0057e80$30ef7d50@kilgore>
On Sun, Mar 06, 2005 at 07:54:06PM +0100, boyd, rounin wrote:
> >Hence the hash builtin...
>
> builtin is not there to fix bugs in $PATH walks.
ENOPARSE. The hash builtin lets you force the
shell to re-examine the path. I didn't comment
on whether or not I thought it was a good idea.
next prev parent reply other threads:[~2005-03-06 19:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 16:31 I RATTAN
2005-03-04 16:35 ` William Josephson
2005-03-04 19:37 ` Russ Cox
2005-03-04 17:19 ` rog
2005-03-05 4:43 ` boyd, rounin
2005-03-05 14:43 ` Sam
2005-03-06 18:47 ` William Josephson
2005-03-06 18:54 ` boyd, rounin
2005-03-06 19:14 ` William Josephson [this message]
2005-04-01 14:39 I RATTAN
2005-04-01 14:51 ` Russ Cox
2006-09-13 21:05 ISHWAR RATTAN
2006-09-13 22:15 ` Russ Cox
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=20050306191411.GA75074@mero.morphisms.net \
--to=jkw@eecs.harvard.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).