http://commandliners.com/2010/01/vim-for-programmers-ii/ # killall -9 X Mon, 09 Jan 2012 20:50:59 +0000 hourly 1 http://wordpress.org/?v= http://commandliners.com/2010/01/vim-for-programmers-ii/comment-page-1/#comment-18493 commandliners » Greping from inside Vim Mon, 09 Jan 2012 20:50:59 +0000 http://commandliners.com/?p=1635#comment-18493 [...] grep command and the results will be integrated into the error list, the one we wrote about in compilation errors. This way, one can move through the matching list using both :cp and :cn We can instruct Vim to use [...] [...] grep command and the results will be integrated into the error list, the one we wrote about in compilation errors. This way, one can move through the matching list using both :cp and :cn We can instruct Vim to use [...]

]]> http://commandliners.com/2010/01/vim-for-programmers-ii/comment-page-1/#comment-8915 commandliners » Vim. Saving keystrokes: abbreviations Fri, 30 Jul 2010 08:16:41 +0000 http://commandliners.com/?p=1635#comment-8915 [...] posts, Vim is the perfect tool if you want to save time in your daily work. It helps you in the write-compile-debug cycle, it indents and autoindents code, it is extremely powerful for searching, replacing and many other [...] [...] posts, Vim is the perfect tool if you want to save time in your daily work. It helps you in the write-compile-debug cycle, it indents and autoindents code, it is extremely powerful for searching, replacing and many other [...]

]]>