[
{
"path": "README.md",
"content": "# Vim Cheat Sheet for Programmers\n\nWhen I was learning Vim I wanted to know a few things:\n\n* How are keys grouped by functionality?\n* What keys are free to re-use?\n* How do I set sane defaults for editing code?\n\n## Screen (150 dpi)\n\n\n\n## Print (600 dpi)\n\n* [vim_cheat_sheet_for_programmers_print_600dpi.png](vim_cheat_sheet_for_programmers_print_600dpi.png)\n\nThe color coded Legend / Keys helps provide guidance for your experience level.\n\n\n\n# Older Versions\n\n## 2.3\n\n* [2.3 pdf](old_2.3/vim_cheat_sheet_for_programmers_print.pdf)\n* [2.3 png](old_2.3/vim_cheat_sheet_for_programmers_print.png)\n* [2.3 xls](old_2.3/vim_cheat_sheet_for_programmers_print.xlsx)\n\n\n## 2.0\n\n* [2.0 pdf](old_2.0/vim_cheat_sheet_for_programmers_print.pdf)\n* [2.0 pdf](old_2.0/vim_cheat_sheet_for_programmers_print.png)\n* [2.0 xls](old_2.0/vim_cheat_sheet_for_programmers_print.xlsx)\n\n# Other cheat sheets / references\n\n* http://www.viemu.com/a_vi_vim_graphical_cheat_sheet_tutorial.html\n* http://tnerual.eriogerg.free.fr/vim.html\n* http://www.lagmonster.org/docs/vi.html\n* http://jrmiii.com/2009/03/06/learning-vim-the-pragmatic-way.html\n* https://vim.rtorr.com/\n* https://devhints.io/vim\n"
},
{
"path": "legend.html",
"content": "\n\n\n\n\n
\n\n| * Green | = Essential (movement) |
\n| * Yellow | = Basic (insert/replace) |
\n| * Orange / Blue | = Advanced (folding/tags) |
\n| * Red | = Expert (macros) |
\n
\n\n\n"
},
{
"path": "old_2.0/index.html",
"content": "\nVim Cheat Sheat for Programmers by Michael Pohoreski\n\n\nUpdate: Version 2.0 is up! There are now 4 versions to chose from:
\n(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.)
\n\n\nThe color coded Legend / Keys helps provide guidance for your experience level.
\n
\n- Green = Essential
\n- Yellow = Basic
\n- Orange / Blue = Advanced
\n- Red = Expert
\n
\nIf you don't like this version (I'd love to hear why) try these, you may find them more to your liking...
\n\nThanks to all the redditors for the feedback! ~ Michael
\n
\nThe on-screen 150 DPI .png version is shown...\n ![](\"vim_cheat_sheet_for_programmers_screen.png\")
\n
\n
\nThe color hard-copy 300 DPI .png version: \n ![](\"vim_cheat_sheet_for_programmers_print.png\")
\n
\nThe monochrome hard-copy 300 DPI .png version: \n ![](\"vim_cheat_sheet_for_programmers_bnw.png\")
\n
\nAn color blind hard-copy 150 DPI .png version: \n ![](\"vim_cheat_sheet_for_programmers_colorblind.png\")
\n\n
\n=== Vim Rants ===
\n
\nVim has 4 bugs...\n\n- Unable to map Caps lock key, Ctrl-1, Ctrl-Shift-1, Ctrl-Alt-Shift-1, etc. !
\n- Unable to distinguish between TAB and Ctrl-I, ESC and Ctrl-[ ! Any _modern_ editor can tell the diffeence. It is not 1970 anymore people!
\n- :set list doesn't work for displaying all whitespace with a seperate character, i.e., listchars is missing an whitespace:+ option.
\n- 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') ....
\n
\nOthe then that, Vim is a beautiful code editor!\n\n\n\n"
}
]