2009 LinuxQuestions.org Members Choice AwardsThis forum is for the 2009 LinuxQuestions.org Members Choice Awards.
You can now vote for your favorite products of 2009. This is your chance to be heard! Voting ends on February 9th.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
vi will do if vim is not avail eg commercial Unices
Ironically, this is exactly the reason I ended up learning VI/Vim oh so long ago.
My favorite editor of all time is TPU, then edit /tpu, then when I had to deal with Unix more I ended up with VI.
There is a TPU type emulation for Emacs, but it doesn't do a very good job (no offense to the dev - it's a nice try). It made it so slow and cumbersome (and simply didn't do a lot of stuff). So back to VI.
VI of course lead to Vim which has become very nearly universal
I will take my Lisp-aware Emacs, thank you very much. Truth be told, though, I have gotten to like VI (VI != VIM).
Could anyone tell me, why no modern, VI(M) implementation has Lisp-mode any more? In my copy of The Ultimate Guide to the VI and EX Text Editors (1990), it says there is a Lisp-mode, but if you check through the man pages for VI on any BSD, they say that Lisp-mode is not yet implemented.
It's there ready in my daily use distro with no frills or fuss. It works so i haven't really tried others. Nice enough gui.
I also like vi when i was stuck on a command-line for a little while. Very nice Scite is pretty. It seems a lot of work has gone into making a lot of nice text-editors to suit different ppl for different purposes. That's what i really like. If i was forced to use only the 1 text-editor i would resent it but having the choice allows me to relax and enjoy it
Distribution: openSuSE 42.1_64+Tumbleweed-KDE, Mint 17.3
Kate vs. Kwrite
I only recently installed KDE 4.x along with SuSE 11.2. There is a new Kwrite there which is a real lot improved over the older version(s). I voted for Kate but I'm not sure that this came about only because I have no experience with Kwrite yet...