Correction this was wrong. IRB isn’t using Powershell’s env variables,
so when I unset all of those variables, Ruby still had them set. My bad.
[mailto:email@example.com] On Behalf Of Jim D.
Sent: Monday, March 23, 2009 10:18 AM
To: firstname.lastname@example.org; Tomas M.
Subject: Re: [Ironruby-core] Mspec errors. Where should I start
So it looks like there are 2 issues here. One is the immediate issue:
You don’t have %HOME% set, which is why this error occurs. Underneath
that there is a real issue: IronRuby isn’t searching for a %HOME%
replacement in the same way that Ruby does. Ruby can find ~ even if
HOME, HOMEDRIVE, HOMEPATH, and USERPROFILE are all unset. I’m not sure
what algorithm they use at that point.
So to contribute:
We need you to follow the steps at
http://wiki.github.com/ironruby/ironruby/contributing, especially the
portion about signing the agreement
If you want to fix this error (which is going to be resolved in
the path referenced below), go for it, then send IronRuby a pull request
on Github. I’ll pull your changes in.
If you want to work on something else, feel free to grab a bug
from RubyForge from the Triaged category after Tomas adds some more
(Tomas, can you add more bugs to that category :))
a. Or, like Shri suggested in the other thread, choose a tag file
and fix all the tags
Let us know if you have any questions!
[mailto:email@example.com] On Behalf Of Adam Kahtava
Sent: Monday, March 23, 2009 5:15 AM
Subject: [Ironruby-core] Mspec errors. Where should I start
When running mspec (mspec -ci core\array\append) I get the following
Invalid argument - ~/.mspecrc (Errno::EINVAL)
Should I be getting this error? How can I resolve this?
I’d like to contribute. Where should I start? Should I be pulling items
from the bug list:
Thanks in advance,