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.
If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/
You can sign-in using OpenID credentials, or register a traditional username and password.
First-time OpenID users will be automatically assigned a username which can be changed after signing in.
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
Same game as #10096 . loop as many times as you like.
In exemple, screen can bind keys to switch between windows. I like to use Ctrl + Arrow to move left or right window. So I bind like this in .screenrc :
bindkey ^[OD prev # Ctl-left, prev window
bindkey ^[OC next # Ctl-right, next window
Exploit that RPM database just sitting there, taking up space.
Consider the following simple situation [ reading something using while and read ]
[See script 1 in sample output]
The variable var is assigned with "nullll" at first. Inside the while loop [piped while] it is assigned with "whillleeee". [Onlly 2 assignments stmts]. Outside the loop the last assigned value for "var" [and no variable] inside the while can't be accessed [Due to pipe, var is executed in a sub shell].
In these type of situation variables can be accessed by modifying as follows.
[See script 2 in sample output]
Vary helpful when reading a set of items, say file names, stored on a file [or variable] to an array an use it later.
Is there any other way 2 access variables inside and outside the loop ??
Automation click every 4 second on a macro slot bar to world of warcraft for prospecting item
enable auto loot and create macro, put mouse over slot on the bar
/use Elementium Ore
Listen to different voices in the system--useful for picking the voice you like
"*" is important if you don't know exact name of file. Check it out and you'll see
There's already a proper command for what the former alternative tried to script
Add an alias to your .bashrc that allows you to issue the command xkcd to view (with gwenview) the newest xkcd comic... I know there are thousands of them out there but this one is at least replete with installer and also uses a more concise syntax... plus, gwenview shows you the downloading progress as it downloads the comic and gives you a more full featured viewing experience.
For those of us that still uses lynx :)
This doesn't work in bash, but in zsh you can typeset -T to bind a scalar variable to an array. $PATH and $path behave this way by default.
Sometimes "ls" is just too slow, especially if you're having problems with terminal scroll speed, or if you're a speed freak. In these situations, do an echo * in the current directory to immediately see the directory listing. Do an echo * | tr ' ' '\n' if you want a column. Do an alias ls='echo *' if you want to achieve higher echelons of speed and wonder. Note that echo * is also useful on systems that are so low in memory that "ls" itself is failing - perhaps due to a memory leak that you're trying to debug.
Best way I know to get rid of .bash_history and don't allow bash to save the current one on exit
Edit: added ~/ before .bash_history, just in case... ;)
Select a file/folder at random.
grep '^[^#]' sample.conf
\__/ |||| \_________/
| |||| |
| |||| \- Filename
| |||\- Only character in group is '#'
| ||\- Negate character group (will match any cahracter *not* in the
| || group)
| |\- Start new character group (will match any character in the
| | group)
| \- Match beginning of line
\- Run grep
Empty lines will also be not matched, because there has to be at least one non-hash-sign character in the line.
Remove your BASH history and then link it to /dev/null
Shows the status of SElinux.
-- fir3net.com --