Hacker News Reader

Comment by patio11 | Hacker News Reader

This solves one of my largest annoyances when using Github as a Rails developer, namely, "Oh yay, time to walk five levels up and four levels down to find the place in the code of this gem where the function caused in the line causing the problem is actually defined."

Previously if I had to do it more than once I would copy the gem to disk, import to Netbeans, and then use Netbean's equivalent function. (Which I use so frequently during development I should really map it to, I dunno, tab.)

View on HN

As a Rails developer I agree, although not as much as a Java developer agrees:

  com/ => company/ => moar_hierarchy/ => etc/ => even_more/ => files

Clicking though all of those empty directories, even with new slide from earlier this year, was still a pain in the butt.

http://p.hagelb.org/maven.jpg

You know, by the spec, you don't actually need levels called "etc" and "moar_hierarchy". You can even skip com if you want.

try http://gemedit.rubyforge.org/

lets you type

     gem edit <gem>

and it opens the gem dir in your $EDITOR

Bundler allows you to do the same thing from a bundled environment with:

bundle open <gem>

with vim, NERDTree, ack, and gem edit: once you `gem edit` and the directory list opens, go to the directory listing (e.g. /Users/you/.rvm/gems/ruby-1.9.2-p136/gems/twitter-1.1.1/) and type "cd". This changes your current working directory to the gem root, which in turn allows you to `:Ack some_text` from the gem root which is very useful.

Or create a little script to launch your editor in the right directory:

  $ echo $GEMEDITOR
  editgem.sh
  $ cat ~/bin/editgem.sh 
  #!/bin/sh
  cd $1 && mvim $1

This is no longer necessary since version 1.0, it now opens your editor from the gem's directory. https://github.com/lmarlow/gemedit/blob/master/History.txt#L...

Reply on news.ycombinator.com