Editors?
I am a Vim guy, of course! And nothing but GNU/Linux works for me!
CS101 was a Fortran course, and I used vi on Linux. (Sorry, RMS, I can't use GNU/Linux everywhere, but I do really mean it. And after meeting you, and attending your talk, I do appreciate the need for using "GNU/Linux" everywhere, but it's just not feasible for me! I try to use it once in the beginning ...)
vi was a real pain. No, I am not criticizing it! vi was written for some specific reasons. See this for some idea. So, I moved over to pico. Atleast, it was much more straightforward, and the menu at the bottom helped too. Let me confess, though, that at that time, both vi and vim meant the same thing to me. I only knew that vim was an improved version, but had no idea what the improvement was. Moreover, pine was another reason I moved to pico - atleast, editing code or email didn't mean I had to switch my keyboard handling contexts (mentally).
I was the first webmaster of Mood Indigo - something I did for MI 96, 97 and 98 - and I had the great fortune of getting in touch with Sitaram Iyer during the course of some MI-related work. He is one of the best hackers I've ever come across! Anyways, the point is this - I was completely swept away by the things that he did with vim. And there was no looking back. An escape for a week from the world of pico (and with a lot of associated pain) meant I escaped to vim forever.
Some pain points remained - What about pine? Well, it allowed using vim as the mail editor! Saved! :)
But it wasn't all that comfortable a feeling. Mutt soon won me over.
So, now for all my programming work, it's vim, exuberant ctags, and the GNU Compiler Collection.
(In one of my posts, I think I'll write something about vim (version 7), ctags, and something that I have very recently discovered - which helped me decide against playing with Eclipse, by the way - icomplete. The combination is just awesome!)
CS101 was a Fortran course, and I used vi on Linux. (Sorry, RMS, I can't use GNU/Linux everywhere, but I do really mean it. And after meeting you, and attending your talk, I do appreciate the need for using "GNU/Linux" everywhere, but it's just not feasible for me! I try to use it once in the beginning ...)
vi was a real pain. No, I am not criticizing it! vi was written for some specific reasons. See this for some idea. So, I moved over to pico. Atleast, it was much more straightforward, and the menu at the bottom helped too. Let me confess, though, that at that time, both vi and vim meant the same thing to me. I only knew that vim was an improved version, but had no idea what the improvement was. Moreover, pine was another reason I moved to pico - atleast, editing code or email didn't mean I had to switch my keyboard handling contexts (mentally).
I was the first webmaster of Mood Indigo - something I did for MI 96, 97 and 98 - and I had the great fortune of getting in touch with Sitaram Iyer during the course of some MI-related work. He is one of the best hackers I've ever come across! Anyways, the point is this - I was completely swept away by the things that he did with vim. And there was no looking back. An escape for a week from the world of pico (and with a lot of associated pain) meant I escaped to vim forever.
Some pain points remained - What about pine? Well, it allowed using vim as the mail editor! Saved! :)
But it wasn't all that comfortable a feeling. Mutt soon won me over.
So, now for all my programming work, it's vim, exuberant ctags, and the GNU Compiler Collection.
(In one of my posts, I think I'll write something about vim (version 7), ctags, and something that I have very recently discovered - which helped me decide against playing with Eclipse, by the way - icomplete. The combination is just awesome!)
posted by Ravindra Jaju at 7:32 AM
0 Comments:
Post a Comment
<< Home