Kevin Le bkad

bkad commented on issue bkad/CamelCaseMotion#18
@bkad

Interesting, mine eats the ." but not the newline, I can take a look.

bkad commented on issue mitsuhiko/platter#7
@bkad

pex doesn't require you to install pex to run the zip files it creates. The zip files are executable on their own, assuming a python interpreter ex…

bkad commented on issue davideast/ng2do#4
@bkad

I was able to run with the current HEAD of angular (angular/angular@821f008) by also merging in #5

bkad opened pull request davideast/ng2do#3
@bkad
Update README.md to specify angular build subdir
1 commit with 1 addition and 1 deletion
bkad pushed to patch-1 at bkad/ng2do
@bkad
  • @bkad b17f2e4
    Update README.md to specify angular build subdir
@bkad
  • @bkad 89940cc
    fix issue with motion between 'CONSECUTIVE ACRONYMS'
bkad pushed to master at bkad/vimconfig
@bkad
bkad reopened issue bkad/CamelCaseMotion#17
@bkad
iw selects spaces and newlines
@bkad
iw selects spaces and newlines
bkad commented on issue bkad/CamelCaseMotion#17
@bkad

test help

@bkad
@bkad
Shifts the beginning of the word by one character
bkad commented on issue bkad/CamelCaseMotion#6
@bkad

Try :set iskeyword? in your vim and see what comes back, it would also affect your motions. Mine for reference is: iskeyword=@,48-57,_,192-255

@bkad
  • @bkad a83bc51
    improve behavior for motion across '.' and '-'
@bkad
motion across '.' and '-'
@bkad
Handle uppercase sequences like a word
bkad commented on issue bkad/CamelCaseMotion#15
@bkad

I've made an adjustment to the way the plugin behaves for consecutive capital characters in 54c1932, and find the behavior to be correct now. I've …

@bkad
  • @bkad 54c1932
    fix for consecutive uppercase letters
@bkad
Buggy motion for consecutive uppercase letters
bkad pushed to angular at bkad/prat
@bkad