"Invalid argument - *" when creating a new rails project

I was having problems creating new projects, so I uninstalled ruby and
rebooted. I then reinstalled ruby with gems from the Ruby-1.8.2-15
installer and then tried to create a new rails project with “rails
depot”.

Now I get:

[c:\dev\ruby\rails]rails depot
create
Invalid argument - *

all the time no matter what directory I’m in.

Any ideas? I’m lost.

rails depot

Not sure if you need the create…

Michael

Jay K. [email protected] wrote:
I was having problems creating new projects, so I uninstalled ruby and
rebooted. I then reinstalled ruby with gems from the Ruby-1.8.2-15
installer and then tried to create a new rails project with “rails
depot”.

Now I get:

[c:\dev\ruby\rails]rails depot
create
Invalid argument - *

all the time no matter what directory I’m in.

Any ideas? I’m lost.


Posted via http://www.ruby-forum.com/.

sorry…I misread your post…obviously this is what you are doing! :frowning:

Michael

Michael [email protected] wrote:
rails depot

Not sure if you need the create…

Michael

Jay K. [email protected] wrote:
I was having problems creating new projects, so I uninstalled ruby and
rebooted. I then reinstalled ruby with gems from the Ruby-1.8.2-15
installer and then tried to create a new rails project with “rails
depot”.

Now I get:

[c:\dev\ruby\rails]rails depot
create
Invalid argument - *

all the time no matter what directory I’m in.

Any ideas? I’m lost.


Posted via http://www.ruby-forum.com/.


Rails mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails


Yahoo! FareChase - Search multiple travel sites in one click.


Rails mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails

icosahedron wrote:

I was having problems creating new projects, so I uninstalled ruby and
rebooted. I then reinstalled ruby with gems from the Ruby-1.8.2-15
installer and then tried to create a new rails project with “rails
depot”.

Now I get:

[c:\dev\ruby\rails]rails depot
create
Invalid argument - *

all the time no matter what directory I’m in.

Any ideas? I’m lost.

It turns out it was 4NT. If I run "rails " from the normal
cmd.exe, it works fine. Go figure. Too bad, as I really like 4NT.

hgs wrote:

On Fri, 18 Nov 2005, Jay K. wrote:

all the time no matter what directory I’m in.

Any ideas? I’m lost.

It turns out it was 4NT. If I run "rails " from the normal
cmd.exe, it works fine. Go figure. Too bad, as I really like 4NT.

Wild guess: On unix :-

/usr/local/bin/rails: executable /usr/local/bin/ruby script

Maybe 4NT is trying to execute rails “directly” rather than
passing it to ruby? I don’t kow anything about 4NT.

    Hugh

4NT is a cmd.exe replacement that includes a number of niceties. If you
develop on NT, you should check it out, but as a replacement, there are
some inherent incompatibilities. I use it so much I forget sometimes
it’s not the default.

Thanks.

don’t you need to install rails

gem install rails

On Fri, 18 Nov 2005, Jay K. wrote:

all the time no matter what directory I’m in.

Any ideas? I’m lost.

It turns out it was 4NT. If I run "rails " from the normal
cmd.exe, it works fine. Go figure. Too bad, as I really like 4NT.

Wild guess: On unix :-

/usr/local/bin/rails: executable /usr/local/bin/ruby script

Maybe 4NT is trying to execute rails “directly” rather than
passing it to ruby? I don’t kow anything about 4NT.

    Hugh