Reddit Reddit reviews Learning the vi and Vim Editors: Text Processing at Maximum Speed and Power

We found 10 Reddit comments about Learning the vi and Vim Editors: Text Processing at Maximum Speed and Power. Here are the top ones, ranked by their Reddit score.

Computers & Technology
Books
Operating Systems
Unix Operating System
Learning the vi and Vim Editors: Text Processing at Maximum Speed and Power
O Reilly Media
Check price on Amazon

10 Reddit comments about Learning the vi and Vim Editors: Text Processing at Maximum Speed and Power:

u/InAQuietCorner · 7 pointsr/learnprogramming

I like this cheatsheet and this book: Learning the vi and Vim Editors.

Edit: I forgot about Vim Adventures!

u/hyperbolist · 4 pointsr/vim

And here are links to buy "Learning the vi and Vim Editors" from O'Reilly and from Amazon, in case you don't want to steal some learning material.

u/reverendj1 · 3 pointsr/linux4noobs

I like to use nano for simple file editing, such as changing a config. For programming, I switched from Gedit to Atom to Vim. This book is what finally made Vim click for me. Following along with that book, after a week, I was just as productive in Vim as I had been in Atom, after using it for 1-2 yrs. My main reason for switching to Vim is that Vi/Vim are a pretty standard default install on most distros, so you're pretty much guaranteed to have it everywhere. I've never tried using emacs, so I can't say anything good or bad about it.

u/sbicknel · 3 pointsr/vim

Don't overlook the included user manual. :help usr_toc will take you there. It is based on the book "Vi IMproved--Vim," which is also available free in PDF format on the Internet because it is published under the Open Publication License. The book is dated, but the manual is up-to-date and tracks with the book very closely.

Derek Wyatt's tutorial videos are good, but there is another vim video tutorial set at Vimcasts.

If you would rather read, but don't want to dig into a five-hundred page book, "A Byte of Vim" may be more manageable. Several of these resources are listed in this subreddit's sidebar.

Several books are now available that cover Vim nicely: "Learning the Vi and Vim Editors," "vi and Vim Editors Pocket Reference," "Hacking Vim 7.2," "Practical Vim: Edit Text at the Speed of Thought," and a brand new book: "Pro Vim," all available on Amazon.

u/nhasian · 2 pointsr/linux4noobs

I got this one a few years ago and it really helped: http://www.amazon.com/Learning-Vim-Editors-Arnold-Robbins/dp/059652983X

u/Amperture · 1 pointr/TwoBestFriendsPlay

So, this was a thought frequently at the back of my mind, but I never did bother to investigate why the fuck O'Reilly uses pencil sketches of ugly animals as their book covers.

So I went to their website, and a few things stuck out to me.

  • The Horrid Little Monkey is actually the primary logo for their website
  • The Horrid Little Monkey is their mascot for their book to learn how to use vim which coincidentally is my favorite text editor
  • They have a page dedicated to explaining why they use ugly animals as mascots, and the explanation boils down to the cover designer is basically just Plague

    >And, as I investigated the attributes of the real animals, I quickly discovered that there were intriguing correspondences between specific technologies and specific animals. That resonance grew and expanded as I learned more about both the technologies and the animals.

    >I was so energized and inspired that I spent an entire weekend working on the covers without much sleep.

    >At the end of the weekend, I gave several sketches to my neighbor to take into the office.
u/ben174 · 1 pointr/vim

Same problem here. No idea on how to fix, unfortunately. I grabbed the O'Reilly book, then played vimgolf religiously for a couple weeks, then forced myself to use vim as my only IDE/text editor for a month, and now it feels more natural to me than any other editor I've used.

u/lavidaesbella · -1 pointsr/learnprogramming

You should not look the source code of the libs if you want to learn how C works, their code it's full of complex concepts of C programming like a lot of preprocessor, abstract structures and complex algorithms (dynamic programming, divide and conquer, backtracking, etc).

If you don't know how UNIX programming works you should start there, like process control, file and dir management, threading, networking. A lot more useful to learn pure C than the standard libs implementations.

For UNIX programming read this: Stevens

To improve your knowledge in C: K&R and as a complement king.

If you insist in reading library implementation take a look at OpenBSD libs implementation (much clutter-less than GNU).

Oh, and also do yourself a big favor and learn Vim reading learning vim.

Knowing the basics of C language and UNIX programming is the way to become a true programmer/hacker.

u/detaer · -2 pointsr/askscience

These books, third one optional are a great start to be a freedomm-beard / community troll like myself. I can't say its a glorious life but it pays the bills. Being able to throw together a cluster of computers for some interesting distributed database / model crunching is pretty damn cool. I would also suggest a copy of virtualbox and ubuntu for a beginner's linux desktop and debian for servers. Freebsd is pretty dame great, and cent/rhel is not a bad place to go either. Its also unix with a U not eunuch with an e.

http://www.amazon.com/Linux-Administration-Handbook-Evi-Nemeth/dp/0130084662
http://www.amazon.com/Practical-Guide-Commands-Editors-Programming/dp/0131367366/ref=pd_sim_b_2
http://www.amazon.com/Learning-Vim-Editors-Arnold-Robbins/dp/059652983X/ref=pd_sim_b_23

I understand this is not so much a scientist bit of content here, but having systems competency if you plan on doing research that does any model analysis is pretty valuable.