-
-
Notifications
You must be signed in to change notification settings - Fork 91
Troubleshooting
If you get errors in the terminal immediately after a message like:
Successfully installed doing-x.x.x
2 gems installed
...it may just be documentation related. If running doing
works, you can ignore them. If not, try running the install command again with --no-document
:
$ gem install --no-document doing
If running doing
after a successful install gives you a "command not found" error, then your gem path isn't in your $PATH
, meaning the system can't find it. To locate the gem and link it into your path, you can try this:
cd $GEM_PATH/bin
ln -s doing /usr/local/bin/
Then try running doing
and see if it works.
Ruby is rife with encoding inconsistencies across platforms and versions. Feel free to file issues (see below).
As a free project, doing
isn't heavily supported, but you can get support from myself and other users on GitHub. If you run into a replicable bug in your environment, please post an issue and include your platform, OS version, and the result of ruby -v
, along with a copy/paste of the error message. To get a more verbose error message, try running GLI_DEBUG=true doing [...]
for a full trace.
Please try not to email me directly about GitHub projects.
Feel free to poke around, I'll try to add more comments in the future (and retroactively).
PayPal link: paypal.me/ttscoff