Getting colors to work for ls and vim on Solaris 11

Just some quick notes, for myself and in case someone else ever wants this. In this day and age, I hate having to setup color on terminals ….colors make things very easy to see, quickly. So here are my notes so i don’t have to go spend time figuring it out yet again lol.

in your .profile or .bashrc
export TERM=xtermc
alias ls=”/usr/gnu/bin/ls -lah –color=auto”

in your .vimrc
syntax on
set showmatch
set bg=dark
set incsearch
set tabstop=4
set shiftwidth=4
set expandtab
set bs=2

bs=2 makes your backspace erase instead of inserting weird chars
syntax=on will enable color
the rest of it is just my personal settins in vim :)

One Comment

  1. Brian Masinick says:

    Good thing that Vim is now available on Solaris! I can still remember the first time I used minicomputer systems in the early eighties running UNIX software. Only the best systems at the time could handle Vi well. I often resorted to using Ed, believe it or not, and it got the job done. Emacs? In the early eighties, forget it!

    The first implementation of SunOS on Motorola 68000 tower systems was promising, but for the first few years, it was underpowered too. It did not take long, however, for most systems, Sun certainly included, to take up the Slack… oh wait, we’re not talking about Slackware, or ARE WE?

    In 1998 I bought my first home PC, a 100 MHz Micron P100 with 16 MB of memory (I believe I added another stick to bring it up to an amazing 32 MB! I had a 2.1 GB hard drive. By then, Elvis could fly on it, and GNU Emacs also worked great. Sun had Sparc, and soon thereafter, UltraSPARC, and we had plenty of system resources. By the change of the millennium, there really was no good reason NOT to have every editing capability you could ask for. If Emacs could come up in 2-3 seconds, ANY Vi provided virtually instantaneous access to files.

    I’ve heard of people editing files a few GB in size, though these DO still stretch the capabilities, not only of the editors, but of virtual memory components. The best ones can actually do it, believe it or not.

    Anyway, thanks for the tips; I often do the same thing; I frequently post my favorite scripts and configuration files in public places, both to benefit others and to have a place where I can grab them, so if I access some other computer, as long as it has Internet access (and the freedom to use it), I can get the tools that I want anywhere.

    Nice simple configuration, Dave, thanks!