Vi/Vim for cli. When in KDE, kedit. Gnome, gedit. Though, I have been known to open a terminal window and use vi while under Gnome/Kde.
Well, for what it is worth, I am going to say that MCedit, which is part of Midnight Commander, is my editor of choice. *It is very simple to use yet powerful and does everything that I need, which is admitted very simple. *I have decided to use LyX for my writing progam and Mozilla Composer for web page stuff. *I am using Pine/Pico for e-mail. *So, my text editor need only handle config files, simple scripts, tuning my html and some playing around with Perl. *
I respect Vi and know how to use it (more or less) , but I really do not like the mode-thing and have always been uncomfortable with it. *
So, there you have it.
Vi/Vim for cli. When in KDE, kedit. Gnome, gedit. Though, I have been known to open a terminal window and use vi while under Gnome/Kde.
Jed was my favorite editor for a long time, and I think it's a nice editor... pretty easy to learn, but powerful enough for most editing tasks... but then I learned vim, got fond of it, then I learned 8)elvis8) and fell in love with it. The keystrokes make much more sense than in jed or emacs.Traditionaly, I've use emacs...but recently my tastes have switched over to Jed
I use elvis for anything that requires a text editor, from editing simple config files to editing web pages. Sometimes when I'm in X, I use the gui version of it.
In case you didn't hear or understand, let me make myself clearer:
8) Elvis 8)
I'll probably get around to learning vim eventualy....but untill then,I know enough to get by if I'm not able to use either jed or emacs on a computer.
if u wanna learn basic editing with vim execute the following command:
vimtutor
15 minutes and u'll know how to use vim
u won't know the advance stuff though (hell, i've been using vim for a couple of months now and i don't know the advance stuff either...), but u'll know how to use it for ur editing needs and u'll fall in love with it
I usually use vi. If I am at a prompt, then its vi. If I am inside X, then its either gEdit or Kwrite. Its just as easy, just more overheadPico is okay, but I can whip through stuff faster now in vi/vim. Why waste more time than necessary? Pico , I must say was a great beginners tool while learning. Emacs was about the most confusing thing to plop down in front of. Then again back then, getting a soundcard working was amazing for any newbie, hehe
My wife bought me a vi reference coffee mug for Christmas. It has vi commands around the mug. It's already transformed the way I work. And it's a jumbo sized mug. You don't meet women like that everydayif u wanna learn basic editing with vim execute the following command:
vimtutor
15 minutes and u'll know how to use vim
u won't know the advance stuff though (hell, i've been using vim for a couple of months now and i don't know the advance stuff either...), but u'll know how to use it for ur editing needs and u'll fall in love with it![]()
I use Gedit and pico.
Probably because I am not familiar with running VIM yet.
I use these to edit my MUD src, area, playerfiles and just about anything else I want.
GEDIT because of the cool goto line # feature. Great for debugging errors.
Ras
Shibby!!! Yay for the wife!!!!!!!!
My wife bought me a vi reference coffee mug for Christmas. It has vi commands around the mug. It's already transformed the way I work. And it's a jumbo sized mug. You don't meet women like that everyday *![]()
Well, after NGene said good things about Jed, I installed it and started using it. And I like it a lot. It seems to be a very solid and powerful editor, yet very easy to use with a clean, friendly interface.
Somehow in my mind I was confusing Joe and Jed and did not realize that Jed was a pretty powerful editor. In Emacs mode, it has all the characteristics that I liked in Emacs, but without the self-contained mini-universe. ;D
NGene, you may have done it to me again...
Bookmarks