ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
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.
I don't use all of their capabilities, so my preference is based on when/where I use them. I'm usually working at the command line so vim is always available. Although I like gvim, I don't always have a GUI available.
I use vim mostly not sure why probably cause I don't bother to compile vim with the gui. Other then that its probably cause when I need vim im in a command box or not in X at all. I probably use mousepad more tho.
I always use gvim called as vim. That way, I can have niceties like the X clipboards and a adjusted xterm title bar, but still maintain a console look+feel because it doesn't open another window like normal gvim does. So my answer is... both.
Cream shapes Vim into an interface you probably already know (sometimes called Common User Access [ext.link] ). Whether you are writing emails or developing large software applications, Cream saves you time and gets you up and running quickly.
vim because I'm used to the cmd line and also I tend to use a minimal set of cmds (too lazy to learn a lot/ don't need them), so nearly anything I do I can do in vi if needed.
Not least because, as noted above, most prod systems don't run a GUI, esp non-Linux type Unices.