Hi Marcel, I looked into the "cmd /c" thing a bit more.  It turns out the
reason it was needed for me was because my nodist path was "C:\Program
Files (x86)\nodist".  If I put the files somewhere else (like
C:\src\nodist) it works. Maybe the .CMD can be updated to handle this
better?  I replaced the note in the readme, though it would be better to
update the .CMD file I do not know how to do that.

  I could make an attempt at adding support for reading .nodeversion file,
but I haven't been able to figure out how to run the existing tests.  Node
is new to me, so if there is some convention I'm missing it.

  My console output from the cmd issue wais:

    C:\Program Files (x86)> nodist update
    \nodist\bin\nodist.cmd"" was unexpected at this time.
    C:\Program Files (x86)> get-command nodist | select path

    Path
    ----
    C:\Program Files (x86)\nodist\bin\nodist.cmd


On Wed, May 15, 2013 at 5:17 AM, Marcel Klehr <notifications@github.com>wrote:

> In README.md:
>
> > @@ -9,6 +9,7 @@ Don't install node beforehand!
> >  2. When you've got the code, add `...path...\nodist\bin` to your path ([how?](http://www.computerhope.com/issues/ch000549.htm)).
> >
> >  3. Now, run `nodist update`, which will install the dependencies.
> > +    * From powershell, use cmd /c "nodist update"
>
> is this really necessary? I think it works fine for me...
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/marcelklehr/nodist/pull/23/files#r4233332>
> .
>