Possible bug about when to seek for tags about targets.vim HOT 4 CLOSED

I will take a look.

from targets.vim.

I can reproduce the behavior and I was surprised as well. But it turns out that that is actually default Vim behavior. To verify that, use vim -Nu NONE to start Vim without any plugins and repeat your test.

I agree that this behavior seems strange. You could ask in the vim-dev mailing list why it works that way and whether it could be fixed. Let me know if you need any assistance with that.

targets.vim is just reusing Vim's tag text objects here to select tags. Only if that fails it seeks into a distant tag. And in this case Vim's tag text objects did work, but not as intended.

I could possibly rewrite the tag text objects without using Vim's tag text objects, but that seems like the wrong approach to me.

Thank you for the heads up and let me know if you want me to ask on vim-dev.

from targets.vim.

Interesting! I agree that it doesn't make sense for targets.vim to rewrite this. I may ask on the vim-dev mailing list, but I won't have a chance this weekend, so it'd have to be next weekend. We'll see if I remember!

from targets.vim.

Actually it is consistent with with the other default text objects. I just tested it on this example:

{
    { some text }
}

With the cursor on the beginning of the middle line, vi{ selects some text and not the full middle line. If you insert any non whitespace between the cursor and the opening { the behavior will change to select the full second line.

So apparently the default text objects seek into the next text object if there is only whitespace between the cursor and the text object.

from targets.vim.