If you have more applications running on your system then your system can handle them then you know what I mean when I say that the Music Players take a lot of CPU. Otherwise harmless, but when you are doing too many things, then lot of times you would feel that probably stopping the Music player might help. But then Linux is all about alternatives. So, there is a command line player called mpg123, which does not use so much CPU. But what about playlist 🙂
(find . -type f |sort -R) > $playlist
trap exit INT TERM EXIT 1 2 3 15
while read line
done < $playlist
Just copy this to somewhere as .sh file or just type this in your directory of choice and it will play all the music in that folder in random order without hogging your CPU.
Now once that is done, you will need to ensure that the call to g++, gcc and others that you want to use, you will need to create a link in the “~/bin” directory, like so:
for i in g++ gcc c++ cc
ln -s $(which colorgcc) ~/bin/$i
The one liner above will create the links for colorgcc as your favourite compiler in your homedir. Don’t forget to add the bin diretory to your PATH variable:
And now finally the ~/.colorgccrc file taken from Ubuntu for your reference:
# colorgcc configuration file
# $Id: colorgccrc,v 188.8.131.52 1999/04/25 15:24:03 jamoyers Exp $
# This file should be named $HOME/.colorgccrc
# The following groups of attributes may be combined for a given color:
# clear black on_black
# reset red on_red
# bold green on_green
# underline yellow on_yellow
# underscore blue on_blue
# blink magenta on_magenta
# reverse cyan on_cyan
# concealed white on_white
# For example, srcColor: bold cyan on_yellow
# gccVersion: if defined, append "-" to the compiler paths
# defined hereunder. Otherwise, those paths remains as is set
# gccVersion: 4.1.1
# Define the paths to the actual location of the various compilers.
# (Currently, colorgcc only understands these: g++ gcc c++ cc g77 f77 gcj)
# Don't do color if our terminal type ($TERM) is one of these.
# (List all terminal types on one line, seperated by whitespace.)
nocolor: dumb emacs
# Text between ` and ' is usually source code.
srcColor: bold cyan
# Text other than a warning or error.
# Warnings and errors both have similar formats:
# Each field may be assigned a different color.
errorMessageColor: bold red
# Possible translations, if you use localized compiler.
# (List all translations on one line, seperated by whitespace.)