uru invoked from unknown shell

Issue #54 resolved
Former user created an issue

I'm having trouble as a new Windows XP user getting pik to behave in both the CMD and Git Bash when it was recommended to me to try out uru.

I've downloaded and moved the uru_rt into my C:\bin folder and both terminals find it there.

uru => command not found

uru_rt admin add system => Registered ruby at 'c\RailsInstaller\Ruby 1.9.3\bin

uru_rt admin add C:\Ruby200\bin => Registered ruby at ...

uru_rt ls => 200p353 ... => * system ...

uru_rt 200p353 => panic: uru invoked from unknown shell {check URU_INVOKER env var) ... and a lot of Go output.

Googling for this error and searching this forum revealed nothing that seemed to help. Being a novice Windows user there's probably a simple explanation so please educate me if you would, thanx, sam

Comments (2)

  1. Jon repo owner

    Uru needs to do some trickery to work in multiple shells. It uses the runtime executable uru_rt in combination with shell specific helper scripts to work. You have install uru to make it create the helper shell scripts for you.

    From the install instructions for Windows users...

    :: assuming C:\tools is on PATH and uru_rt.exe was extracted to C:\tools
    C:\tools>uru_rt admin install
    

    To fix your specific issue when running via via cmd.exe, I think this will get you going:

    cd C:\bin
    uru_rt admin install
    cd C:\Some\Where\Else
    uru ls
    uru p353
    uru ls --verbose
    

    Currently uru isn't supported in Git Bash (or MSYS/MSYS2) on Windows. Another user mentioned it but didn't open up a feature request. I assumed it wasn't an important use case.

    That said, if it's important enough to you please open up a feature request and I'll look into it. Essentially, I think it will take convincing uru that bash-on-windows is a valid combination and update it's PATH and GEM_HOME values appropriately. Don't know how tricky this could get or whether it's simple.

    Regardless, if the above uru_rt admin install fixes your issue when using cmd.exe, please close this issue. If not, show what you did with results and will figure out another fix.

  2. Log in to comment