diff --git a/_posts/2010-09-17-installing-gems-skipping-rdoc-and-ri.markdown b/_posts/2010-09-17-installing-gems-skipping-rdoc-and-ri.markdown new file mode 100644 index 0000000..aae063d --- /dev/null +++ b/_posts/2010-09-17-installing-gems-skipping-rdoc-and-ri.markdown @@ -0,0 +1,29 @@ +--- +layout: post +title: Installing gems skipping RDoc and RI +author: David Padilla +email: david@crowdint.com +avatar: d32b52ec6403614b1adf3e648cbbe584 +published: true +--- + +Because, let's be honest, these days, we're always connected to the internet. + +Personally, I've never used the RDoc included on gem installations. + +If I need info about a class, method, module, I ask uncle *Google*. + +Besides, it gets kind of annoying, specially when there's gems that take longer to generate the RDoc, than it takes for the actual gem to install. + +So, here's a tip for those who don't want to wait for gem to install RDoc you'll never use. + +It is as simple as, opening or creating a *.gemrc* file in your home directory, and adding the following line: + +{% highlight bash %} +gem: --no-rdoc --no-ri +{% endhighlight %} + +And that's it. You're setting those options as default when using the gem command. So, the next time you install a gem, it will skip the part where it compiles the gem's documentation. + +There you go, enjoy! + diff --git a/_posts/INCOMPLETE-a-helpful-gem-setting.markdown b/_posts/INCOMPLETE-a-helpful-gem-setting.markdown deleted file mode 100644 index a057a91..0000000 --- a/_posts/INCOMPLETE-a-helpful-gem-setting.markdown +++ /dev/null @@ -1,9 +0,0 @@ ---- -layout: post -title: A Helpful gem setting -author: David Padilla -email: david@crowdint.com -avatar: d32b52ec6403614b1adf3e648cbbe584 -published: false ---- - diff --git a/_site/2010/07/11/git-initial-configuration.html b/_site/2010/07/11/git-initial-configuration.html index 68cc674..21e3664 100644 --- a/_site/2010/07/11/git-initial-configuration.html +++ b/_site/2010/07/11/git-initial-configuration.html @@ -136,16 +136,16 @@
Because, let's be honest, these days, we're always connected to the internet.
+ +Personally, I've never used the RDoc included on gem installations.
+ +If I need info about a class, method, module, I ask uncle Google.
+ +Besides, it gets kind of annoying, specially when there's gems that take longer to generate the RDoc, than it takes for the actual gem to install.
+ +So, here's a tip for those who don't want to wait for gem to install RDoc you'll never use.
+ +It is as simple as, opening or creating a .gemrc file in your home directory, and adding the following line:
+ +gem: --no-rdoc --no-ri
+
+And that's it. You're setting those options as default when using the gem command. So, the next time you install a gem, it will skip the part where it compiles the gem's documentation.
+ +There you go, enjoy!
+ + +Crowd Interactive is an American web design and development company that happens to work in Colima, Mexico... Read More...
+Because, let's be honest, these days, we're always connected to the internet.
+ +Personally, I've never used the RDoc included on gem installations.
+ +If I need info about a class, method, module, I ask uncle Google.
+ +Besides, it gets kind of annoying, specially when there's gems that take longer to generate the RDoc, than it takes for the actual gem to install.
+ +So, here's a tip for those who don't want to wait for gem to install RDoc you'll never use.
+ +It is as simple as, opening or creating a .gemrc file in your home directory, and adding the following line:
+ +gem: --no-rdoc --no-ri
+
+And that's it. You're setting those options as default when using the gem command. So, the next time you install a gem, it will skip the part where it compiles the gem's documentation.
+ +There you go, enjoy!
+ + +It happens, the project and the team grows, and now, there's a bunch of branches in your git repo. It's called branchitis, and it happens to everyone at some point.
- -If you're lucky enough to be working on a Mac, odds are that you're using gitx to watch over your git repos. You're not?! Shame on you.
- -Anyway, so, you open gitx, and all you see is a bowl of spaghetti
- - - -So, if you want to see a specific branch, you can call gitx from the command line and specify the branch you want to see
- -$ gitx feature2
-
-Nothing out of this world here, since you can do the same thing by using the built in dropdown on gitx to select the branch you want to see, but, did you know that you can specify more than one branch?
- -So, let's say you want to merge the feature2 and the feature5 branch, but first, you want to see how the branches are related. You can call gitx from the command line and specify both branches as the arguments.
- -$ gitx feature2 feature5
-
-Then you'd get something like this:
- - - -Cool! You can actually read this first hand, and it's faster than trying to descipher the spaguhetti.
- -In case you're wondering, yes, you can specify 3 branches, or as many as you'd like to see. Go ahead, try it out.
- -Hope this helps you in some way,
- -Cheers.
- - -
Click here for Comments
+