Andri Möll
Andri Möll
Absolutely! I haven't yet decided which solution would be most appropriate. @tpope has [Projectionist.vim](https://github.com/tpope/vim-projectionist). Perhaps Node.vim can somehow configure that for use in JavaScript projects...
I've started using Projectionist.vim myself and it works well. I wonder what default mappings should Node.vim set up. Any ideas, @nathanielescribano?
Hey! Thank you, @huangyg11, for drawing attention to this! Sorry about the confusion! I will add a note to the README to make it more clear! Or would you expect...
Hey! Thanks. I'll look into that. I haven't yet gotten on the Io.js wagon myself, but given that it's often symlinked as `node`, might make sense to open the right...
Ugh, both Io.js and Node.js don't return their name on `--version`. I guess that means having to check if `node` is a symlink...
I meant checking if it symlinks to a binary named `iojs`, not that it's merely a symlink. Running help before `--version` would work, too.
It still points to a binary named `iojs`. :)
I suspect that's because the package resolution algo I wrote for Node.vim isn't seeking for modules recursively up the chain. 😇 I should fix that as I occasionally hit that...
Hey, Sorry for any problems! Could this be related to https://github.com/moll/vim-node/pull/6?
Hey, Thanks for the report. I'll see what I can find out!