|
You are here |
shrik3.com | ||
| | | | |
nvie.com
|
|
| | | | | Where I lay out the recent changed I made to my Vim setup. | |
| | | | |
www.outcoldman.com
|
|
| | | | | If you are working in terminal - one of the important things is to keep your scripts and dotfiles in the order. Basically, you should consider them as one of your regular pet/side projects, and as any other of your pet projects: you should be able to easily contribute to it; you should have a good way to maintain dependencies; you should make it reusable; I am a Terminal user, I use combination of tmux, zsh and vim for everyday development. In this post I just want to share with you my dotfiles and few ideas/plugins I use to maintain my scripts and configuration. Hope that it may be useful for you as a reference. | |
| | | | |
spf13.com
|
|
| | | | | [AI summary] Steve Francia shares his comprehensive and well-organized .vimrc configuration file designed for efficient editing on a UNIX command-line interface. | |
| | | | |
cyberchris.xyz
|
|
| | | Intro So after picking up Vim less than a year ago, and spending a lot of time with it, I can say for sure it is the best text editor I have ever used. Okay, that's all the Vim propaganda you'll find in this post. The main aim of this post is to get people new to Vim into a comfortable environment, while also teaching you how to get plugins into your vim config since you'll probably want to customize it, once you get a feel of Vim. | ||