I've been using the "/bin/cp" command for years installing vim plugins and it's worked remarkably well; requiring just about 1 invocation on average...
What problem does that thing solve?
21–30 of 119 posts
I've been using the "/bin/cp" command for years installing vim plugins and it's worked remarkably well; requiring just about 1 invocation on average...
What problem does that thing solve?
Awesome work! Cheers airblade. One nitpicky thing though, why do you use "_" and not "-" for removed lines? Can't see why you wouldn't want it vertically centered!
Compare:
25 - def foo():
26 baz()
With: 25 _ def foo():
26 baz()
(Where there used to be a bar() call before baz().) The first version makes it look like the `def foo():` was somehow removed.An aside question; what's the deal with "pathogen"? I've been using the "/bin/cp" command for years installing vim plugins and it's worked remarkably well; requiring just about 1 invocation on average... What problem does that thing solve?
ETA: also note that git-cloning into bundle means that upgrading is just a question of entering the plugin directory and running git pull.
Is this expected? I save quite frequently, it's an unconscious reflex at this point.
An aside question; what's the deal with "pathogen"? I've been using the "/bin/cp" command for years installing vim plugins and it's worked remarkably well; requiring just about 1 invocation on average... What problem does that thing solve?
Earlier quoted context omitted.
You can achieve that manually with `highlight clear SignColumn` in your colour scheme or ~/.vimrc. I'll (I'm the author) probably make this the default because it seems quite a common wish.
I've added it at the bottom of ~/.vimrc, but for some reason it doesn't work until I explicitly type `highlight clear SignColumn` while editing a document. Any ideas why this could be happening? Great plugin by the way, super handy.
au VimEnter * highlight clear SignColumn
An aside question; what's the deal with "pathogen"? I've been using the "/bin/cp" command for years installing vim plugins and it's worked remarkably well; requiring just about 1 invocation on average... What problem does that thing solve?
Also it makes it easier to update, since all you need to do is replace the folder with the newer version and you're all set.
I've also got a similar plugin https://bitbucket.org/sirpengi/iwilldiffer that works with hg as well as git. Mine uses python though, nice to see an implementation that's all in viml. Neither of our plugins are async though (so vim ui will block while the diff is running), which is the biggest hurdle I want to cross.
As far as I know Vim is single-threaded; you can't run operations asynchronously.
An aside question; what's the deal with "pathogen"? I've been using the "/bin/cp" command for years installing vim plugins and it's worked remarkably well; requiring just about 1 invocation on average... What problem does that thing solve?
Earlier quoted context omitted.
I've added it at the bottom of ~/.vimrc, but for some reason it doesn't work until I explicitly type `highlight clear SignColumn` while editing a document. Any ideas why this could be happening? Great plugin by the way, super handy.
I had the same problem, I did: au VimEnter * highlight clear SignColumn