-
Notifications
You must be signed in to change notification settings - Fork 0
/
README
34 lines (27 loc) · 1.35 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
have my ~/.vim directory under version control and my "real" vimrc (the one with all my settings) inside that directory, at ~/.vim/vimrc:
~/
---- .vim/
---- ---- (plugins and stuff)
---- ---- vimrc
---- .vimrc
My regular ~/.vimrc has only one line:
runtime vimrc
No need to create symlinks or whatever.
This is how I would push my config on a new machine where Git has already been installed:
$ cd
$ git clone [email protected]:romainl/dotvim.git .vim
$ echo "runtime vimrc" > .vimrc
What follows is the whole creation process. I assume that you have created an account and a repo named "vimconfig" on Github and that you already have a lovingly crafted ~/.vimrc and a well organized ~/.vim/.
$ cd
$ mv .vimrc .vim/vimrc
$ echo "runtime vimrc" > .vimrc
$ cd .vim
$ git init
$ echo "This is my Vim config." > README
$ git add *
$ git commit -m "My Vim config is versioned."
$ git remote add origin https://github.com/username/vimconfig.git
$ git push origin master
At that point, you should have the same content on Github and in your local repository.
You manage that repository normally and push your commits when you are ready. Simple.
Note that the whole Github thing is only useful if you need/want to sync your config on multiple machines or, somehow need/want to share it with others. If you don't, there's no obvious point.kPOKA VIM on CB.