Skip to content

A bare Vim environment, plus Pathogen, powered by Docker

Notifications You must be signed in to change notification settings

jeremyckahn/vim-docker-env

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

22 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

vim-docker-env

Dockerhub Repo

A lightweight Vim environment powered by Pathogen, vim-plug, and Docker

This repo is an educational tool to be used at jeremyckahn's Vimconf.live workshop session. It should work on OS X, Windows, and Linux.

About the speaker

Click to expand

Hello! I'm Jeremy Kahn, a Senior UI Engineer at Rally Health. I've been using Vim for about 9 years and love it for its customizability and efficiency. When I'm not making videos about how I tweak Vim to tame gnarly codebases, I like to develop open source web games and animation tools.

jeremyckahn's github stats

Installation (please do this before the workshop begins!)

Step 1: Install the environment

  1. Install Docker
  2. Clone this Git repo. (git clone https://github.com/jeremyckahn/vim-docker-env.git)
  3. cd into this repo.
  4. Run this command at the root of this repo:

On Linux and OS X:

docker run -it --rm -v "$(pwd)":/home/vimuser jeremyckahn/vimconf.live:latest

On Windows (must be done in Powershell):

docker run -it --rm -v ${PWD}:/home/vimuser jeremyckahn/vimconf.live:latest

From here you'll be in a Linux-based container environment. The home directory configuration files in this environment are the same as the ones in the Git repo root. Modifying a home directory file in the container will modify the same file in the host environment (and vice-versa).

Step 2: Install the plugins

Once in the Linux environment, you can boot Vim with vim. From here enter :PlugInstall to install the plugins that we'll go over in the workshop. Once that process is complete, you can either enter :Reload or simply quit Vim and boot it up again for the changes to take effect.

Note: To get back into this Vim environment again later, you'll just need to run the docker run command from step 1 as you did the first time. You won't need to do step 2 again, as the files installed by that step were placed in the Git repo on your host machine, which persist across Docker container instances.


Why is this presentation using Docker?

While an entire Docker container isn't necessary to run Vim as it's configured here, it provides a consistent environment for all session participants as well as an easy setup. You could even use it as a starting point for your own Vim-based IDE, if you wanted to!

About

A bare Vim environment, plus Pathogen, powered by Docker

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages