Vim for Humans

Post by dllthomas » Mon, Oct 17, 2016, 5:08 PM UTC

MichaelGG wrote: post #35

gravypod wrote: post #10

I wish I could use vim or emacs. I don't know if I'm stupid or something but all of the key bindings, everything you have to remember, it just doesn't make sense to me. I wish there was something like nano + plugins. If I had that I could implement most of what I need (other then auto-completion for a crap load of languages).

Try out Vim Adventures to get some basic commands down. Then find Vim emulation for your editor of choice. Leave it in insert mode as much as you need at first. Slowly you'll start using more Vim commands. In a while you'll wonder how you ever edited without it.

Post by patrickdavey » Mon, Oct 17, 2016, 5:11 PM UTC

gbrown_ wrote: post #3

I've only skimmed this but there seems to be a focus on customizing and plugins from the get go. I think it's worth getting to know Vim "as is" before doing such things. Indeed there certainly some things that aren't the most useful or obvious but it's good to understand their original intent. Not to crap on the author of this but I'd recommend Drew Neil's Practical Vim over this (and pretty much every other Vim book…

Post by dllthomas » Mon, Oct 17, 2016, 5:19 PM UTC

AdmiralAsshat wrote: post #20

dsr_ wrote: post #8

Earlier quoted context omitted.

In my experience, most native English speakers are easily confused about who vs whom, and avoid whom by rephrasing: Who is this book for?

Which is okay in conversation, but in writing, your pedantic editor or proofreader would probably inform you that it is considered poor style to end the sentence on a preposition. So he's basically trading one error for another. Who/whom is indeed awkward at first to remember, but the phrase "for whom" tends to sound better on the tongue than some of the others due to its inclusion in the title "For Whom the Bell Tol…

Post by a3n » Mon, Oct 17, 2016, 5:19 PM UTC

gbrown_ wrote: post #3

I've only skimmed this but there seems to be a focus on customizing and plugins from the get go. I think it's worth getting to know Vim "as is" before doing such things. Indeed there certainly some things that aren't the most useful or obvious but it's good to understand their original intent. Not to crap on the author of this but I'd recommend Drew Neil's Practical Vim over this (and pretty much every other Vim book…

Post by jeremiahwv » Mon, Oct 17, 2016, 5:27 PM UTC

clifanatic wrote: post #23

gbrown_ wrote: post #3

I've only skimmed this but there seems to be a focus on customizing and plugins from the get go. I think it's worth getting to know Vim "as is" before doing such things. Indeed there certainly some things that aren't the most useful or obvious but it's good to understand their original intent. Not to crap on the author of this but I'd recommend Drew Neil's Practical Vim over this (and pretty much every other Vim book…

I always thought that if I were ever to write a book on vim, I'd start with a thorough introduction to ed, followed by a thorough introduction to ex, finally followed by a thorough tutorial on all the features of plain-old vanilla vi, only then to introduce the vim parts and macros and graphics and things.