|
You are here |
blog.sanctum.geek.nz | ||
| | | | |
sidneyliebrand.io
|
|
| | | | | In my never ending quest for an optimal Vim setup I am always looking for ways to improve. I've used Vim for about two months now and I'm still learning a lot. In this post I'm going to take you through a part of my .vimrc that describes my non-plugin key binds. | |
| | | | |
countvajhula.com
|
|
| | | | | ||
| | | | |
ismail.badawi.io
|
|
| | | | | I use vim. I've used vim since I started programming; the very first program I wrote - hello world in C, following along a cprogramming.com tutorial - was typed out in vim, inside a cygwin environment on Windows. Naturally, at first it was hard and intimidating. I didn't know how to do anything, least of all edit text. I learned about insert mode and normal mode. I learned about navigating using hjkl, and deleting the current line with dd, and saving and quitting with :wq, and for a long time that was it. | |
| | | | |
blog.dataumbrella.org
|
|
| | | [AI summary] An article by Rebecca BurWei explains the fundamentals of Bash scripting, covering techniques for automation, error handling, logging, and option parsing within data science workflows. | ||