Daniel Hahler

If we also host e.g. ubuntu-vims on the Docker Hub repo, we could have automated builds for Vim master then (https://hub.docker.com/add/automated-build/testbed/). In this case there should be probably a separate...

> A GH org might be needed as well. Probably that would be the best. OTOH we basically only need a user and could do it from Travis then -...

Oh, regarding Vim I have vimjas.. ;) https://github.com/vimjas Makes sense for vim-testbed at least. Maybe we could ask to join testbed also..

FWIW, https://hub.docker.com/r/testbed/vim is used by now, but still only manually. What would be required is setting up pushing from GitHub Actions, after https://github.com/Vimjas/vim-testbed/pull/78. It could get triggered when a tag...

Makes total sense. > testbed.vim would be a dangling file analogous to .travis.yml. Can you elaborate what you mean with "dangling" here, please? I suggest then also to include some...

> The container `ENTRYPOINT` script runs `exec su -l vimtest -c "env VIM_TESTBED=1 /vim-build/bin/$BIN $ARGS"`. Shouldn't it still `cd /testbed`? Did I understand it correctly that `/testbed` replaces `/testplugin`? I...

Note that it is also referenced in https://github.com/jmozmoz/compactheader/blob/77b40358c2799557a10fb68e02cdff900f95d497/build.xml#L6, but that should likely be kept?

Thanks. > Link on github top page also need to be updated. Yeah, that's the one I've used.

At the top of https://github.com/jmozmoz/compactheader.

Likely. Interesting idea. Needs to detect the preview window though, of course - and that does not have a specific buftype/filetype. Would need to investigate. Just out of interest: do...