-
Notifications
You must be signed in to change notification settings - Fork 0
namavivarjita/VIMPOKA
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
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.
About
POKA's VIM
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published