Many programming guides recommend to begin scripts with the #! /usr/bin/env shebang in order to to automatically locate the necessary interpreter. For example, for a Python script you would use #! /usr/bin/env python, and then the saying goes, the script would “just work” on any machine with Python installed. The reason for this recommendation is that /usr/bin/env python will search the PATH for a program called python and execute the first one found… and that usually works fine on one’s own machine.
Die EU-Unterhändler versichern: TTIP und Ceta werden keine europäische Standards verwässern. Dabei wurden Umwelt- und Nahrungssicherheitsregeln längst geschwächt.
Save a file you edited in vim without the needed permissionsI often forget to sudo before editing a file I don't have write permissions on. When you come to save that file and get the infamous "E212: Can't open file for writing", just issue that vim command in order to save the file without the need to save it to a temp file and then copy it back again. :w !sudo tee % Annotated link http://www.diigo.com/bookmark/http%3A%2F%2Fwww.commandlinefu.com%2Fcommands%2Fbrowse%2Fsort-by-votes
commandlinefu.com is the place to record those command-line gems that you return to again and again. Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
A repository for the most elegant and useful UNIX commands. Great commands can be shared, discussed and voted on to provide a comprehensive resource for working from the command-line