-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
Using gf, etc, for AMD module paths. #11
Comments
Hey! Thanks for the idea. I'll see if I can come up with something. ;-) |
Holy smokes I would love this for when I add my source directory to NODE_PATH |
This might be relevant https://github.com/kana/vim-gf-user |
Hi @moll, any update on this feature? |
I'd love the integration with |
I've written a small plugin that should help out with this case. It works alongside vim-node and provides configurable resolution for each project as well. Let me know if there's anything that could be added that could help out! https://github.com/tomarrell/vim-npr |
Hi, I like the idea of being able to use
gf
to open files from the path in the text, but it'd be nice if this worked for other package systems like AMD, etc.I've got this:
If I put my cursor on
'js/mpq/layouts/results/unit-details'
then I get an error:Obviously this is because it's not a Node.js module, and the
js
folder is actually../../../js
.Is there a way to configure paths for a project so if it doesn't find the file, it can check the path list or similar? Maybe something like
and it could be saved in the project folder and I could source it.
The text was updated successfully, but these errors were encountered: