On Tuesday, July 12, 2016 at 12:34:43 PM UTC-5, Henrik Giesel wrote:
> Given: I open vim -u NONE a.c
>
> When: I type ifoo('bar','(','(');<esc>F,vib
>
> Then I expect: have ('bar','(','(') selected
>
> What actually happens: Nothing is selected
>
>
> I always thought this was weird. Why are those stray parentheses algorithm of
> finding braces this much?
>
>
> When I have some colors installed in vim, it is able to detect any kind of
> strings. And given Vim can detect if any given character is part of a string
> or not, it should also be smart enough to know, that it shouldn't match those
> with the % or * operators, or any of theib, ab family.
>
>
>
I confirm, this looks like a bug. From the help, I would expect ib and ab to
select an area defined by the [( and ]) motions. But [( and ]) at the same
cursor location jump to the expected text. These motions additionally respect
the cpo-% flag (or lack thereof).
Furthermore, if you put a linebreak after that last comma, the text object
selects the expected text. It looks like only the special case where the
opening and closing parenthesis are on the same line is broken.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
