Ken Powers

If I were to guess it's choking somewhere around here: https://github.com/sheerun/vim-polyglot/search?q=haxehilink

This is something [Prosemirror](http://prosemirror.net/demo/collab.html#edit-Example) has gotten working, and they have a similar method of handling documents from what I can immediately tell (immutable data structure decoupled from the DOM).

The [ProseMirror solution](http://marijnhaverbeke.nl/blog/collaborative-editing.html) is almost like OT but operations have to be applied in order. It works more like a rebase. If I understand it correctly the client attempts to...

Just my two cents -- I am 100% against block-level locking, however much simpler it may be. Google Docs set a precedent of how collaborative editing should work and anything...

+1 for this feature. I use `gciw` and `gcf,` a lot with https://github.com/tomtom/tcomment_vim (commenting out individual function parameters).

You should also look at what is preferred for whatever environment you happen to be developing in. For example, the React community tends to prefer Webpack whereas Aurelia would have...

Probably worth pointing out that these are called [Tagged Template Strings](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings#Tagged_template_strings).

Perhaps a generic storage provider interface.

@nickcolley That looks nice but optional persistence would still be awesome.

No, because sometimes different browsers have different property names and webkit sometimes has multiple prefixes to support older webkits. Consider the following base flexbox code: ``` css display: -webkit-box; display:...