Allow generation for types after cursor

[ouuan]

For example, if the cursor is at the beginning of a line starts with some whitespace:

    int foo();

I'll need to move the cursor to int or further to call Neogen.

An inline forward search may solve this problem.

[danymat]

Hello ! This is tricky, because Neogen currently generates when you are "inside" (that means, inside any subnode of desired content.)
If we allow this behavior, what happens if this int foo(); is already inside something else (for example a function) ? Will we call the annotations for the function or the type ?

Maybe Neogen could process itself 2 times:

• First time: locate next upper node that matches Neogen requested "type".
• Second time (like a fallback): if nothing found, locate the first node in the same line that matches the requested type.

[danymat]

This is a good idea, but could be a "breaking" change, because it can modify some process in someone's workflow.
It's a very good idea, after consideration.

[ouuan]

I just realized that mapping to $<cmd>Neogen<cr> works for me. It may not work in some other use cases, though.

[danymat]

I will put this idea on hold, asking for more feedback on users. I feel like this is a too much important change to do, without asking for more input

[danymat]

Hello, after giving more though on this, I find that this is not optimal, and thus for multiple reasons:

• The user should have a predictable guess of what annotation will be generated. As mentioned here: Allow generation for types after cursor #53 (comment), this will be very unpredictable, even if I want to come up with the solution I proposed.
• This feature will add a complexity to the code where it is not required: going with my solution, that would required fetching the nodes and doing multiple times the same loop, in order to find the best node
• Lastly, finding a node in the same line in Treesitter is currently a pain to do so, because that will require to filter every nodes and only keep ones that start at the current line. The other way around is not possible, aka: fetching nodes for a specific line

I'm sorry if this answer does not satisfy you, feel free to reopen this issue if you find some counterarguments on what my takes, or if you want to contribute to the issue. Nevertheless, thanks for the suggestion !
Cheers 🙂 😃