Repository: Michaelangel007/vim_cheat_sheet
Branch: master
Commit: 5cd309d6ab44
Files: 10
Total size: 6.5 KB
Directory structure:
gitextract_wpx1vh81/
├── README.md
├── bad_cheat_sheets/
│ ├── fixed_BYeUs9t.xcf
│ └── problems_BYeUs9t.xcf
├── legend.html
├── old_2.0/
│ ├── index.html
│ ├── vim_cheat_sheet_for_programmers_bnw.xlsx
│ ├── vim_cheat_sheet_for_programmers_colorblind.xlsx
│ ├── vim_cheat_sheet_for_programmers_print.xlsx
│ └── vim_cheat_sheet_for_programmers_screen.xlsx
└── old_2.3/
└── vim_cheat_sheet_for_programmers_print.xlsx
================================================
FILE CONTENTS
================================================
================================================
FILE: README.md
================================================
# Vim Cheat Sheet for Programmers
When I was learning Vim I wanted to know a few things:
* How are keys grouped by functionality?
* What keys are free to re-use?
* How do I set sane defaults for editing code?
## Screen (150 dpi)
## Print (600 dpi)
* [vim_cheat_sheet_for_programmers_print_600dpi.png](vim_cheat_sheet_for_programmers_print_600dpi.png)
The color coded Legend / Keys helps provide guidance for your experience level.
# Older Versions
## 2.3
* [2.3 pdf](old_2.3/vim_cheat_sheet_for_programmers_print.pdf)
* [2.3 png](old_2.3/vim_cheat_sheet_for_programmers_print.png)
* [2.3 xls](old_2.3/vim_cheat_sheet_for_programmers_print.xlsx)
## 2.0
* [2.0 pdf](old_2.0/vim_cheat_sheet_for_programmers_print.pdf)
* [2.0 pdf](old_2.0/vim_cheat_sheet_for_programmers_print.png)
* [2.0 xls](old_2.0/vim_cheat_sheet_for_programmers_print.xlsx)
# Other cheat sheets / references
* http://www.viemu.com/a_vi_vim_graphical_cheat_sheet_tutorial.html
* http://tnerual.eriogerg.free.fr/vim.html
* http://www.lagmonster.org/docs/vi.html
* http://jrmiii.com/2009/03/06/learning-vim-the-pragmatic-way.html
* https://vim.rtorr.com/
* https://devhints.io/vim
================================================
FILE: legend.html
================================================
| * Green | = Essential (movement) |
| * Yellow | = Basic (insert/replace) |
| * Orange / Blue | = Advanced (folding/tags) |
| * Red | = Expert (macros) |
================================================
FILE: old_2.0/index.html
================================================
Vim Cheat Sheat for Programmers by Michael Pohoreski
Update: Version 2.0 is up! There are now 4 versions to chose from:
(If you are wondering what the differences are between the screen and print: the screen has less color variations, and no gradients to make it easier to read.)
The color coded Legend / Keys helps provide guidance for your experience level.
- Green = Essential
- Yellow = Basic
- Orange / Blue = Advanced
- Red = Expert
If you don't like this version (I'd love to hear why) try these, you may find them more to your liking...
Thanks to all the redditors for the feedback! ~ Michael
The on-screen 150 DPI .png version is shown...
The color hard-copy 300 DPI .png version:
The monochrome hard-copy 300 DPI .png version:
An color blind hard-copy 150 DPI .png version:
=== Vim Rants ===
Vim has 4 bugs...
- Unable to map Caps lock key, Ctrl-1, Ctrl-Shift-1, Ctrl-Alt-Shift-1, etc. !
- Unable to distinguish between TAB and Ctrl-I, ESC and Ctrl-[ ! Any _modern_ editor can tell the diffeence. It is not 1970 anymore people!
- :set list doesn't work for displaying all whitespace with a seperate character, i.e., listchars is missing an whitespace:+ option.
- The cursor movement keys h j k l are literally hard-coded throughout the source -- which also effects the netrw :Explore file browser. A user should be able to tell Vim what their 4 basic movement keys are, and ALL commands & Plugins should use THAT. The PROPER way to write code is to translate key presses into an enumeration, i.e. CMD_MOVE_UP, CMD_MOVE_DOWN, etc, and use THAT in your logic, NOT if (cmd == 'h') ....
Othe then that, Vim is a beautiful code editor!