Request: add to tag stack when using ALEGoToDefinition OR add a ALEGoBackFromDefinition

[dylan-chong]

Vim shortcuts pair <C-]> and <C-t> nicely. With ALEGoToDefinition, there isn't a nice equivalent jump back command (e.g. <C-t> ALEGoBackFromDefinition or <C-t>) which would be nice to have.

[w0rp]

You can use <C-o>. See :help jump-motions.

[chaucerbao]

I've been using <C-o> as well, but the main difference is that <C-t> returns to the point where the previous <C-]> jump was made.

With <C-o>, you step backwards through all the jump movement history you may have made while looking around the definitions, and jumping into deeper definitions.

A <C-t> would be nice, but <C-o> is workable.

[dylan-chong]

@chaucerbao Yup. That's actually why i mentioned this issue.

@w0rp Is it possible for ALEGoToDefinition to increment the tag stack so we can use C-t to jump back?

[w0rp]

Okay, what is a tag stack, and how do I increment it?

[dylan-chong]

h tag && h tagstack.

I'm not an expert on vim so you may want to get a second opinion before implementing this feature. Maybe this isn't a good idea for some reason we don't know about, or maybe there is a nice solution we don't know about.

[dylan-chong]

On second thought, I am considering that better possible solution would be to have the existing ALEGoToDefinition, add a new ALEGoBackFromDefinition (or some other name), and have some optional way to seamlessly integrate Ale with the C-t and C-] shortcuts (by having an option for the a ALE commands to manipulate the tag stack). This way we don't force any unexpected behaviour upon the tags system, while giving vim users the option for convenience.

I would still definitely need some extra opinions on the above ideas. I am not 100% confident that either of the above options are the best solution

[w0rp]

What would this new command do that Ctrl+O doesn't do already?

[dylan-chong]

As @chaucerbao said, C-o is not the same as C-t. vim help menus will tell you more about them

I was thinking that ale would use its own internal stack that has the information required for ALEGoBackFromDefinition to work.

[w0rp]

I think the right thing to do is to update the tag stack, and add an option for disabling that behaviour. That will probably make everyone happy.