Hi, I want to improve my code navigation skill and I am glad I found combobulate. I am trying to adapt it for Rust. However, I run into an issue that I am not able to navigate to some node.
My cursor is at f the first call_expression. I want to navigate to f2 which is the second call_expression but I am not able to do so. I tried combobulate-navigate-next but it doesn't work for me. I think combobulate considers my current node is at identifier node which has the same start position as call_expression node. Is there a way to tell combobulate to select the parent node to disambiguate my intention?
I just tried it out and yeah there's apparently a bit of a problem with overlap here; if call_expression is removed from the navigable node types, the code seems to work fine.
Hi, I want to improve my code navigation skill and I am glad I found combobulate. I am trying to adapt it for Rust. However, I run into an issue that I am not able to navigate to some node.
For example, I have setup combobulate as such
I have reduced my use case to a snippet
print from tree-sitter-debug-mode
My cursor is at
f
the first call_expression. I want to navigate tof2
which is the second call_expression but I am not able to do so. I triedcombobulate-navigate-next
but it doesn't work for me. I think combobulate considers my current node is atidentifier
node which has the same start position ascall_expression
node. Is there a way to tell combobulate to select the parent node to disambiguate my intention?