jdonaldson/vaxe

Jump to symbol def

fullofcaffeine opened this issue · 5 comments

fullofcaffeine commented

Hey Justin,

Is there any way to jump from a method call/class symbol to the actual class/method definition in the source file? It'd be nice to study the Std (or other libs) as you go.

Cheers,

  • Marcelo.
jdonaldson commented

The way that I have this working now is using ctags. It should be easy to install, and is part of most developer's tool kit. Generate a tags file in the working directory by calling vaxe#Ctags(). I have it mapped to a leader command (which is a bit crude, if you come up with something better let me know):
https://github.com/jdonaldson/dotfiles/blob/87c3d66ec663f58090a9ddf69e548b7192b80b3a/vimrc#L136

This function is special because it uses your hxml build file to tag classes used in your project. This will include classes from your installed haxelibs, as well as the std classes in your haxepath.

You can jump to function/class/etc. definitions by using CTRL-], or the :tag command. Check :help for "tag" for more info.

fullofcaffeine commented

Thanks for the insights. Will do that :-)

fullofcaffeine commented

I installed exuberant-ctags, but calling:

:call vaxe#Ctags()

just seems to fail silently. Is there any way to see the output of this viml function? How would you go about debugging it ?

If I run it manually in the test project dir, like this:

$ ctags --languages=haxe *.hx

I do get a tags file for the test hx classes.

Cheers,

  • Marcelo.
jdonaldson commented

That's strange.

I have a debug flag for vaxe, and I've pushed an update for the bundle so that debug info is provided for vaxe#Ctags().

To enable debug mode, you just set a variable as a command, or in your vimrc:

:let g:vaxe_logging=1

let me know what you see.

jdonaldson commented

closing this out, it's stale.