(Part 2) Top products from r/vim

As others have mentioned, trying to use Vim as an IDE is thinking about the problem or Vim in an inverse manner that will lead to frustration. The Acme Text Editor's model for composing tools to form an IDE is exactly how one uses Vim most effectively.

A concrete Vim specific example is programming Go in Vim: VimGo. Note how in the context of Go instead of subsuming the functionality of external tools, the external tools are instead leveraged and exposed through an interface or accessed through existing Vim functionality.

That is exactly how to wield Vim and external tools masterfully and with the most efficacy. The Unix as an IDE articles discuss this concept in depth also and are excellent. Separation of concerns is precisely how all tools should be designed, something which Plan 9 and Inferno OS display masterfully and irrefutably; note how well done, completely encapsulated abstractions enable a completely composable environment as a result, brilliant no?

That same pursuit is realized through the Go toolchain, much of Haskell, and increasingly through the Clang toolchain, which is very powerful and very freeing to create great, completely optimized workflows.

If you really want to grok the mindset and approach to wielding external tools effectively and why tools must be designed this way for maximum workflow efficacy, I highly recommend reading and understanding the literature written by Brian Stuart's Principles of Operating Systems: Design and Applications that covers Inferno OS's design very well, and W. Richard Stevens' Advanced Programming in the UNIX Environment, the latter of which is a classic CS text and very lucid. Cat-V has a lot of great articles which discuss various tools as well.

The workflows enabled through the UNIX Philosophy is so much more effecient that even when outside a UNIX environment I utilize the tools through a VM rather than being hamstrung in an environment which eschews that design completely.

And because these tools are ubiquitous I can avoid relearning how to accomplish the same thing over and over as a result, meaning that the initial opportunity cost is worthwhile in the long run. Linux is increasingly incorporating features in the kernel which improve upon previous implementations as well as in user space, so it is an exciting time for system programmers as well as other programmers.

Actually, thank you sir, this is that exact type of feedback I was looking for! Thanks for really reading carefully and walking through the book.

As for to the critic, it's quite straightforward, but I don't see any rudeness.

Clearly the book is more like a pure idea now, there is a long way to go (and I'm clearly settled to walk the walk). I always keep in mind the Pixar movies that are absolute crap at the beginning (according to https://www.amazon.com/Creativity-Inc-Overcoming-Unseen-Inspiration/dp/0812993012) and have to walk through multiple sometimes painful transformations until they finally become the masterpieces they are.

I also have to say, that I need to keep my audience in mind. If I wanted to be pedantic I could just as well print out the :help manual. What I want instead is to create something pragmatic and practical, lite and simple, something people outside of the Vim community could grasp and be productive.

The idea is get more people familiar with Vim, so that they can then go deeper after that, maybe join the /r/vim/ and learn from people like you ;)

Anyway, thanks again for the fantastic feedback!

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.

I suggest getting a book, since they are typically far more readable.

I first learned Vim with Steve Oualline's book.

More recently, Drew Neil's Practical Vim and Modern Vim are excellent choices.

Your local public library may well have some good books on Vim as well, if not these exact titles.

> did you just make this up?

Not at all. Tenrecs figure prominently in the book that I’m currently
reading: The Song of the Dodo
by David Quammen. The little critters are kind of like the super heroes
of island biogeography.

holy shit that is awesome. hahaha.. lol. My next question may be a little bit unrelated but where/when/how did you pick up on reg-ex? This is also a skill I have been meaning to pick up but the task justs intimidates me for some reason... i purchased O'Reilly's Regular Expressions Cookbook a few months back and started reading the first bit of the book and just found it impossible to keep with it as my semester started getting heavy..(18 credit hours!). I know it's an essential skill to have and can't help but feel that I shouldn't have to read a 400 page book to master it. Are they really that complicated or do you think I would be alright just diving in next time I need to search for some text and then using the book and the internet as resourses?

lol. did you get that from here??