Some interesting hacks to change the terminal look & feel

What's under the hood of GNU core utilities ? Very interesting diagrams built after reading the source code.

TL;DR :
use : '"'"'" (ie : single + double + single + double + single quote)

Details in the article.

TL;DR : remplacer le contenu de la barre d'adresse par "cmd" + ENTER

Pas sûr que ça me serve souvent, mais okazou ;-)

(via : http://bookmarks.ecyseo.net/?JXd5Kg)

If you write software, config files, makefiles, test cases, or any part of the software delivery ecosystem with hardwired paths to things embedded in them, you are officially a big bozo. Not the fun kind with a red nose and big shoes either. The only hardwired path that's OK is /bin/sh on a shebang line. But if you do things like this:

   #!/usr/bin/python

You should be sent to work 1st level phone support on the midnight shift in Somalia until you learn better. Grrrrrr.

This is the right way to do this is:

   #!/usr/bin/env python

env can reliably be found there and it will "discover" where python happens to actually be installed on that machine, so long as it is in $PATH somewhere. Similarly, learn to use constructs like:

   DATE=$(which date)

   DATE=${DATE:-/bin/date}

In short, NEVER make assumptions where things are. Always discover it at configuration time.

Un jour ou l'autre, on est un boulet...

Certaines astuces sauvent des vies :-D

BTW, it's still in beta, so this _may_ be fixed by the release time...