Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
"enable syntax highlighting
:colorscheme peachpuff (on my system)
Make certain that the syntax line is not commented out, and syntax highlighting is turned on.
For colorschemes, on SuSE, they're in two locations:
if v:lang =~ "utf8$" || v:lang =~ "UTF-8$"
set nocompatible " Use Vim defaults (much better!)
set bs=2 " allow backspacing over everything in insert mode
"set ai " always set autoindenting on
"set backup " keep a backup file
set viminfo='20,\"50 " read/write a .viminfo file, don't store more
" than 50 lines of registers
set history=50 " keep 50 lines of command line history
set ruler " show the cursor position all the time
" Only do this part when compiled with support for autocommands
" In text files, always limit the width of text to 78 characters
autocmd BufRead *.txt set tw=78
" When editing a file, always jump to the last cursor position
autocmd BufReadPost *
\ if line("'\"") > 0 && line ("'\"") <= line("$") |
\ exe "normal! g'\"" |
" add any database in current directory
cs add cscope.out
" else add database pointed to by environment
elseif $CSCOPE_DB != ""
cs add $CSCOPE_DB
" Switch syntax highlighting on, when the terminal has colors
" Also switch on highlighting the last used search pattern.
if &t_Co > 2 || has("gui_running")
You may not have vi aliased to vim.
The original vi does not have colours, it's a straight monochrome editor.
however a lot of systems alias vi => vim, which is vi_improved, which does colours and a lot more.
I have this cmd at the bottom of my .bash_profile file:
Thank you all.
The developers of FC4 changed the script for vi, under /etc/profile.d/ named vimrc.sh.
There are two lines that were added (lines 3 and 4). If you comment these out, you get vi aliased to vim. Go figure. Actually, I think that commenting only #4 will do the trick as well.
I personally think that there's an error in the script.
It runs the id command with the -u option, which generates a zero as a reply if you're root (root's uid is 0). It compares that number to 100, and if it's equal or less, it runs the "return" command, i.e. gets out of the script.