This view lists all the slides from the talk in a continuous format. There is a PDF version available, suitable for printing on A4 paper. The slides are also designed to be viewed as a slideshow from this file with Mozilla or a compatible browser. JavaScript is used to make pressing N progress to the next slide. The slides fit on a 1024 × 768 pixel display. To toggle full-screen mode in Mozilla pr

Vim editor is hands-down the best editor on Unix and Linux environment. These 10 practical tutorials will help you become proficient in the Vim editor. If you are spending lot of time on Unix environment, you should become comfortable in the Vim editor. These tutorials contain practical examples that are designed to give you a jumpstart on the Vim editor fundamentals. This is lot of reading. Don’t

To follow this article the reader should at least have a basic idea of how to use Vim and its command modes. Or if you are new to Vim, you can read my first blog to know how I came in to Vim and its fundamental differences with other editors. Here I'm trying to explain how to make the Vim more productive by adding some extra features through Vim plugins. After this setup the Vim would have most of

These pages contain some vim tips. They are somewhat advanced, and meant for people that have been using vim for a semester or two already. Please see our Editors page if you're looking for begining editor information. Once you've looked at these pages, check out www.vim.org for more tips and plugins. Try "Search for Tips" with no keywords to get the highest rated tips!

Vim is one of the most popular text editors for Linux and Unix systems. Its text-based interface may look intimidating for newcomers, but underneath it there is a wealth of functionality to be learned. Experienced Vim users often feel much more productive using Vim than GUI-based text editors. I've been using Vim on a daily basis for years to do a wide range of tasks, from casual editing of short

Memory allocators divide up memory into pieces. But how can an allocator's author allocate memory to track the pieces? The shells used in terminals – Bash, zsh, etc. – are little compilers wrapped in a loop. We build one with working pipes. Data compression can be simple. Huffman coding, as used in ZIP, MPEG, and MP3, is built around one clever use of a tree. We build six fundamental programming t

I’ve had an off/on relationship with Vim for the past many years. Before, I never felt like we understood each other properly. I felt that the kind of programming I’m doing is not easily done without plugins and some essential settings in .vimrc, but fiddling with all the knobs and installing all the plugins that I thought I needed was a process that in the end stretched out from few hours to week

Using vim is like talking to your editor in ‘verb modifier object’ sentences, turned into acronyms learn some verbs: v (visual), c (change), d (delete), y (yank/copy). these are the most important. there are otherslearn some modifiers: i (inside), a (around), t (till..finds a character), f (find..like till except including the char), / (search..find a string/regex)learn some text objects: w (word)

If you spend a lot of time typing plain text, writing programs or HTML, you can save much of that time by using a good editor and using it effectively. This paper will present guidelines and hints for doing your work more quickly and with fewer mistakes. The open source text editor Vim (Vi IMproved) will be used here to present the ideas about effective editing, but they apply to other editors jus

It all started out innocently enough. You experimented with it once or twice in your first year of college, but Nano and Pico were easier—closer to what you had already been using during high school on the Windows machines and Macs. But as time went on and you got more experience under your belt in the college-level computer science courses, you started to notice something: All of the really great

Posted on September 20th, 2010. I'm a programmer. I work with text files for 6-12 hours every weekday so I care about the text editor I use. If switching to a different editor can increase my efficiency by even 10% it would save a good chunk of my time and let me get back to making cool things. I don't buy the "you're thinking 90% of the time and only typing 10% of the time, so your editor doesn't

Posted on September 6th, 2011. A while ago I wrote a post about switching back to Vim. Since then I've written two plugins for Vim, one of which has been officially "released". A couple of people have asked me if I'd write a guide to creating Vim plugins. I don't feel confident enough to write an official "guide", but I do have some advice for Vim plugin authors that might be useful. Other People