Alternate motions involving brackets.

[paulgittings]

Can the alternative motions "i]", "i}", "i)", i">" be implemented to select everything in between the specified bracket types. so that "yi>" would yank everything within the "<" and ">".

Also the "a" versions "a]", "a}" which are similar to the above but include the brackets in the selection.

[Kazark]

I love how just watching this repository is a great way to learn things about Vim.

[jaredpar]

I'll take a look at getting those implemented.

@Kazark yeah. Before I started writing VsVim I thought I was an average level vim users. Now I know that I maybe knew 5% of what vim was capable of. It's crazy.

[paulgittings]

Thanks Jared.

Just in case you missed it while I just happen to use the closing brackets, the sequences also work if the opening brackets are used eg "yi(" I don't think there is any difference between using open and closing brackets but haven't paid enough attention to be sure.

Also beware that it's not just simply a match to the previous and next bracket, it takes into consideration nesting. For example consider "{ some text { some inner text) cursor is here }"
If "yi}" is pressed when the cursor is on a piece of text in "cursor is here", then the yank will pull " some text { some inner text) cursor is here " and not " some inner text) cursor is here "

[paulgittings]

Jared,
just sat down with a guy at work to show him this "issue" and on his set up the motion works. Must be something wrong with my setup. I'll investigate more.

BTW, the feature list on the wiki doesn't mention these motions (or at least I couldn't find them), which is why I assumed the issue was with VsVim.

Sorry for the confusion.

I'd close this issue off until I figure out if there is a real issue.

[jaredpar]

@TaffyDownUnder the documentation for them in the supported feature section is at the very bottom.

Text object selections (aw, (, {,) ...

Easy to miss and I'm also not the best at keeping that list up to date :(

Have you taken a look at your _vimrc? It's possible there is a key mapping in there which is changing the behavior of the motions in a way that isn't supported by VsVim.