.gemrc Management

[justinbkay]

I think that it would be worthwhile to allow the setting of no rdoc and no ri from this tool. Not sure if this is in the scope of what you are looking to do here.

~/.gemrc

install: --no-rdoc --no-ri
update: --no-rdoc --no-ri

[remear]

This feature has been listed on my whiteboard for a long time but never added here. Thanks for bumping this up in the priority list. I'm still working out the best way to handle reading and modifying the gem settings. Some people get very touchy about a GUI application touching their configs.

[justinbkay]

Is there a way to just write a separate file that you could just include into the gemrc file? Write out the file with your custom settings in it and just add that include line into the gemrc file...

That might be a minimal impact, I don't know.

[remear]

I find most JewelryBox users, myself included, like to use a mix of both JewelryBox and command-line interaction with RVM. Coming up with a solution where you can edit the config manually and via JewelryBox without stepping on toes is unfortunately more difficult than it sounds. Using a config in the way you suggested might cause precedence issues where you expected a behavior but it doesn't work in the current environment like you expected and may end up causing more annoyance than it's worth. I think I have a good idea on how to make this happen but I need to find time to make sure to read through all the Gem documentation to make sure to incorporate all the available options.

Rest assured, it's in the feature list but probably below the new UI update and the overall improvement of the Gemset area to actually make that useful =)

[justinbkay]

Well, good luck to you sir.

On Feb 16, 2012, at 8:00 PM, Ben Mills wrote:

I find most JewelryBox users, myself included, like to use a mix of both JewelryBox and command-line interaction with RVM. Coming up with a solution where you can edit the config manually and via JewelryBox without stepping on toes is unfortunately more difficult than it sounds. Using a config in the way you suggested might cause precedence issues where you expected a behavior but it doesn't work in the current environment like you expected and may end up causing more annoyance than it's worth. I think I have a good idea on how to make this happen but I need to find time to make sure to read through all the Gem documentation to make sure to incorporate all the available options.

Rest assured, it's in the feature list but probably below the new UI update and the overall improvement of the Gemset area to actually make that useful =)

---

Reply to this email directly or view it on GitHub:
#79 (comment)

[remear]

@justinbkay Would you send me a gist of your gemrc. I'm gathering as many as I can find to get good baselines for adding this feature.

[justinbkay]

Sure, pretty boring though.

https://gist.github.com/1921203

On Sat, Feb 25, 2012 at 3:50 PM, Ben Mills <
reply@reply.github.com

wrote:

@justinbkay Would you send me a gist of your gemrc. I'm gathering as many
as I can find to get good baselines for adding this feature.

---

Reply to this email directly or view it on GitHub:
#79 (comment)

Sites:
http://byufootballapp.com
http://broncodashboard.com
http://jbkayconstruction.com
https://twitter.com/justinbkay
http://justinbkay.tumblr.com

It always takes longer than you expect, even when you take into account
Hofstadters Law.

• Hofstadters Law

[mtheoryx]

Here's mine, if it helps at all:

https://gist.github.com/1942898

[remear]

All .gemrc's help. Please spread the word!
https://twitter.com/#!/remear/status/173239398324912128https://twitter.com/remear/status/173239398324912128https://twitter.com/remear/status/173239398324912128https://twitter.com/remear/status/173239398324912128https://twitter.com/remear/status/173239398324912128https://twitter.com/remear/status/173239398324912128

On Wed, Feb 29, 2012 at 10:52 AM, David Poindexter <
reply@reply.github.com

wrote:

Here's mine, if it helps at all:

https://gist.github.com/1942898

---

Reply to this email directly or view it on GitHub:
#79 (comment)