Ambrose Chua

I think the third approach, but with JavaScript, would be better until there is a new web standard to allow styling/tweaking SVG from `` tags. - Performance impact only on...

Experiments with the approach I suggested above: https://github.com/rust-lang/book/compare/d34ea0538f9eeb7457f480fa432ff91075e0b8cf...serverwentdown:experimental-svg-inliner

Additionally, include this block (or equivalent) in your Corefile: ``` # This is used to resolve CNAME records by the `file` plugin. Modify accordingly . { forward . 1.1.1.1 1.0.0.1...

I'm willing to implement but first I want to get some comments from the community.

The protocol _should_ be backward compatible with Python 2 versions of CoVim. Haven't tested.

That was the major reason behind completely dropping Python 2 support. Ubuntu/Debian repositories default to a version of Vim without Python 2 compiled. But then again, if someone can come...

@narfman0 Whoops, I meant Ubuntu's vim-nox package compiles only Python 3 support. Ubuntu (and [Debian](http://vi.stackexchange.com/questions/779/how-do-i-get-vim-to-be-able-to-run-both-python-and-python3-on-a-linux-system-in) repositories don't have both compiled in at the same time, so using Python 3-only bundles...

@capgadsx I might take a look at writing integration tests.

Official reference: https://github.com/docker-library/official-images#consistency

@rugk I would say that by Docker recommendations, the `caddy` docker image ships with a shell and therefore the entrypoint shouldn't be `caddy` (point 3). And since no initialisation is...