If you're using a stack which lets you use SASS, you can use the lighten function:
***
$linkcolour: #0000FF;

a {
color: $linkcolour;
}

a.lighter {
color: lighten($linkcolour, 50%);
}
***

In an ideal world you'd achieve this simply using the following css
***

***

Terminal = An interface that provides a display for output and a keyboard for input to a shell session.

Shell = Interpreter that executes commands typed as strings

Console: Actually two types of console we use:

Physical console =The hardware display and keyboard used to interact with a system
Virtual console = One of multiple logical consoles that can each support an independent login session.
tty (teletype i.e., terminal) = A terminal is a basically just a user interface device that uses text for input and output messages.

The du command shows the disk usage of the file.

The -h option shows results in human-readable form (e.g., 4k, 5M, 3G).

du -h (file name)

The du command shows the disk usage of the file.

The -h option shows results in human-readable form (e.g., 4k, 5M, 3G).

du -h (file name)

Either way works, but they don't do the same thing: the elements of PATHare checked left to right. In your first example, executables in ~/opt/bin will have precedence over those installed, for example, in /usr/bin, which may or may not be what you want.

In particular, from a safety point of view, it is dangerous to add paths to the front, because if someone can gain write access to your ~/opt/bin, they can put, for example, a different ls in there, which you'd then probably use instead of /bin/ls without noticing. Now imagine the same for ssh or your browser or choice... (The same goes triply for putting . in your path.)

Syntax:
***
scp
***
To copy a file from B to A while logged into B:
***
scp /path/to/file username@a:/path/to/destination
***
To copy a file from B to A while logged into A:
***
scp username@b:/path/to/file /path/to/destination
***

Install your foo.deb file with dpkg -i foo.deb. If there are some errors with unresolved dependencies, run apt-get install -f afterwards.

You could also use find and sed, but I find that this little line of perl works nicely.
***
perl -pi -w -e 's/search/replace/g;' *.php
***
-e means execute the following line of code.
-i means edit in-place
-w write warnings
-p loop over the input file, printing each line after the script is applied to it.
My best results come from using perl and grep (to ensure that file have the search expression )
***
perl -pi -w -e 's/search/replace/g;' $( grep -rl 'search' )
***

Ctrl-Q

To disable this altogether, stick stty -ixon in a startup script. To allow any key to get things flowing again, use stty ixany.

ps: It's neither the terminal nor the shell that does this, but the OS's terminal driver.

On Unix-like operating systems (including BSD, GNU/Linux and Mac OS X), tilde often indicates the current user's home directory: for example, if the current user's home directory is /home/bloggsj, then cd, cd ~, cd /home/bloggsj or cd $HOME are equivalent. This practice derives from the Lear-Siegler ADM-3A terminal in common use during the 1970s, which happened to have the tilde symbol and the word "Home" (for moving the cursor to the upper left) on the same key.

On Unix-like operating systems (including BSD, GNU/Linux and Mac OS X), tilde often indicates the current user's home directory: for example, if the current user's home directory is /home/bloggsj, then cd, cd ~, cd /home/bloggsj or cd $HOME are equivalent. This practice derives from the Lear-Siegler ADM-3A terminal in common use during the 1970s, which happened to have the tilde symbol and the word "Home" (for moving the cursor to the upper left) on the same key.