Re: Rails on a Mac, so strange (to me) behavior
- From: Joshua Ballanco <jballanc@xxxxxxxxx>
- Date: Sat, 9 Jun 2007 02:23:32 +0900
Grant Hollingworth wrote:
You don't need to use ./ when you already have a directory name
('script' in this case) in the command.
'script/server' is the same as './script/server'.
You only need ./ if you are already in the same directory as a command.
cd script
./server
Also, adding '.' to your PATH is generally a bad idea. You might end up
running a command you didn't expect.
Yeah...I'm not really sure what I was thinking (probably shouldn't post
before morning coffee...). As for the wisdom in adding '.' to PATH, my
rule of thumb has always been NEVER for root/superuser accounts,
normally no for user accounts, but for dev accounts (where I'll be
compiling a lot of test code into directories not in PATH) it can be a
bit of a time-saver. Oddly, though, I still end up typing
'./my_ruby_prog.rb' half the time...
Cheers (and hope everything for the OP is working now!),
Josh
--
Posted via http://www.ruby-forum.com/.
.
- References:
- Rails on a Mac, so strange (to me) behavior
- From: Mark
- Re: Rails on a Mac, so strange (to me) behavior
- From: Joshua Ballanco
- Re: Rails on a Mac, so strange (to me) behavior
- From: Grant Hollingworth
- Rails on a Mac, so strange (to me) behavior
- Prev by Date: Re: Mexican Blanket (#127)
- Next by Date: (Newbie) Class constants from included modules
- Previous by thread: Re: Rails on a Mac, so strange (to me) behavior
- Next by thread: Re: Rails on a Mac, so strange (to me) behavior
- Index(es):
Relevant Pages
|