christoffer/takunomi-blog
1
0
Fork 0
forked from ohayo-jacob/takunomi-blog
Code Pull Requests Activity

first edit of vim article

Browse Source
This commit is contained in:
jacob 2018-02-24 22:29:55 +01:00
parent 456194e6d7
commit 702661e39b
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
drafts/vim.md Normal file
View File

@ -0,0 +1,12 @@
![](/../images/2017-12-02/a.png)
<time datetime="2017-12-02">2017-12-02</time>
before learning to use Vim, I was intrigued by it, but had a really hard time undeesranding why anyone wouæd go to the trouble of learning to use such a difficult control scheme. Well, the answer was... there isn't that much to learn. If you have a regulare keyboard for example, there is no reason to start using hjkl instead.
Second, coding is often mostly about editing, and boy does vim make that easier:
Cut all inside deliminator and go into insert mode? c+i+[deliminator]. Cut the next two lines? 2+d+d. Change a word? c + i + w + [new word].
Do that again somewhere else? Just press period. There are variations to these actions, but it's mostly stuff like that, that is so amazing when using Vim. Editing is _quick_!
The problem is that normal actions are a bother for a first time: Search for a word? Press forward slash. Save? press colon + w. Quit? Colon + q. Open another file while inside Vim? Colon + e and then write the fucking path yourself you lazy millenial. Or install plugins. Fucking plugins. It's insane to ask that as the first thing, but you will god damn need some plugins.