Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

question: why not TAGS? #30

Closed
ghost opened this issue May 26, 2016 · 1 comment
Closed

question: why not TAGS? #30

ghost opened this issue May 26, 2016 · 1 comment

Comments

@ghost
Copy link

ghost commented May 26, 2016

it would be helpful to me to know why I should use dumb-jump instead of TAGS. Personally, I generated TAGS files but what was missing was I couldn't just jump to the definition of a Rails function or the class that I was using in a Node project.

It might be helpful for others to compare and contrast the difference between using TAGS and dumb-jump.

@jacktasia
Copy link
Owner

My understanding is that TAGS takes a non trivial amount of time to setup for a project and it needs to stay up-to-date. So for this reason TAGS was never an attractive option for me. I wanted something with basic functionality that "just worked" for new projects.

If I am wrong about the above -- or it doesn't apply to you -- and you're happy with TAGS then I am not sure there's any advantage to using dumb-jump.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant