Gaveen's Blog - Archive (2005 - 2017)

More than a year ago I wrote about my story of switching (completely) to Vim as my primary editor. If you have worked in a Unix/Linux system seriously then you know why your editor (whatever it maybe) is a big deal. If you don't, let's just say as a SysAdmin and a budding DevOps type guy, my editor is a serious thing to me. So here's my Take Two. Why? If you are asking why I would want to write about a boring topic again, then this post of obviously not for you. This post is for anyone who's interested in using the mighty and great Vim editor and it's variations (Eg: vim, gvim, etc.) properly. What has changed? I had pushed my Vim configuration to a GitHub repo named gavim and had been using it for a while. And couple of people even forked the repo. Despite how proud I was about my editor configuration, ;) there were some obvious problems. First, a few things were broken (Eg: proper snippet usage) and some plugins weren't working any-more (Eg: Fuzzy_...

Pagers If you use a Linux/Unix system using a pager should be quite familiar to you. A pager in the Unix sense is a program which lets you view pages of contents. Examples for pagers are the Unix commands " less " and " more ". It's likely that your man page viewer is also using one of these. The program less is perhaps the most popular of these, with more features than " more ". These pagers are nice to use use and come very handy in day to day Linux/Unix operations. When you just need to view a file (instead of opening it for editing) it's quite natural to use less. If it's a file with a few lines we'd usually use cat , but less is more convenient on longer files. One irritating thing about less is, there is no syntax highlighting support there by default. You can try to use an external program like " highlight " for the highlighting part and then pipe it to less . (Eg: $ highlight --ansi --force my_file | less -R ) But ...

My Editors I have used many text editors. Some for specific tasks such as LaTeX editing (Eg: Texmaker ), coding (Eg: gedit with plugins ) and the others for more generic text editing. As a system administrator I have been using Vi / Vim all along for editing configuration files and the likes. It was always convenient as almost every Unix system has vi/vim. For me the first Unix editor I used was Emacs . I felt more at home with Emacs key combinations than a hard to fathom Vim modes. Time passed and after a little while, I got used to basic Vi concepts. Since then all of my editing in command line was done in vi/vim. As I've said recently, I have been transforming myself from a sysadmin to a sysadmin/developer kind of person. For coding purposes I used gedit. Some people might think of gedit as the notepad.exe of Linux, but that's so not correct. In fact gedit is a powerful text editor with a lot of plugins to extend it's capabilities. For example there there are plugins f...

I know I have been away from this blog for quite a long time. It's been just over 6 months since I've blogged. There are reasons and other stories. But apart from all of those, I'm glad I am writing here again. I don't know how often I'll be writing again, certainly not once a day (like I ever did that). However I'm hoping now I'll have freedom to write whenever I feel like. But the best way to keep in touch with me is to follow me on Twitter . Here's a brief account of how my life's been during the past few months which saw me transform significantly. Microblogging First thing which slowed down my blogging is microbloggin. Yes, I got in to Twitter early last year and since then never look back. I'm an avid Tweeter and it has become a part of my daily routine. One cool thing I like about Twitter is it's no nonsense and does just one thing, and one thing properly. It lets me keep in touch with like minded people and share information as a side...