| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
defined until after the vimrc file is read (i think?)
|
| |
|
| |
|
|
|
|
| |
config options
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
to start with, and start insert mode after that
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
defined, not local to where the Textobj function is defined
|
|
|
|
| |
character before a comma is a non-whitespace character
|
|
|
|
| |
before running the function
|
| |
|
|
|
|
| |
startline[argbegin - 2] is what we expect
|
| |
|
|
|
|
| |
next line
|
|
|
|
| |
weird like change the buffer
|
| |
|
|
|
|
| |
seems to match their behavior better
|
|
|
|
| |
this will break text objects with boundaries at the ends or beginnings of lines again
|
|
|
|
| |
still not great
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
side effects
|
| |
|
| |
|
|
|
|
| |
probably not working yet, and empty lines still mess things up
|
| |
|
| |
|
|
|
|
| |
/, since there's no good way to tell which direction to look for the closing /
|
| |
|
| |
|
| |
|
|
|
|
| |
line functions at the moment
|