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.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10
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:
This allows you to search through your history using the up and down arrows ? i.e. type "cd /" and press the up arrow and you'll search through everything in your history that starts with "cd /".
Finds all files recursively from your working directory, matching 'aMethodName', except if 'target' is in that file's path.
Handy for finding text without matching all your files in target or subversion directories.
"What it actually shows is going to be dependent on the commands you've previously entered.
When you do this, bash looks for the last command that you entered that contains the substring "ls", in my case that was "lsof ...". If the command that bash finds is what you're looking for, just hit Enter to execute it. You can also edit the command to suit your current needs before executing it (use the left and right arrow keys to move through it).
If you're looking for a different command, hit Ctrl+R again to find a matching command further back in the command history. You can also continue to type a longer substring to refine the search, since searching is incremental.
Note that the substring you enter is searched for throughout the command, not just at the beginning of the command." - http://www.linuxjournal.com/content/using-bash-history-more-efficiently
# Search for an available package on Debian systems using a regex so it only matches packages starting with 'tin'.
Read all chapters up to 'Jumping', improve your effectiveness of wirking in terminal.
Most useful are the Moving and Searching commands
Use the following key binding to search
----------------------------------------------------------------
ng
: Jump to line number n. Default is the start of the file.
nG
: Jump to line number n. Default is the end of the file.
/pattern
: Search for pattern. Regular expressions can be used. [/ = slash] Press / and then Enter to repeat the previous search pattern. Press ESC and then u to undo search highlighting.
n
: Go to next match (after a successful search).
N
: Go to previous match.
mletter
: Mark the current position with letter.
'letter
: Return to position letter. [' = single quote]
'^ or g
: Go to start of file.
'$ or G
: Go to end of file.
s
: Save current content (got from another program like grep) in a file.
= or Ctrl+g
: File information.
F
: continually read information from file and follow its end. Useful for logs watching. Use Ctrl+c to exit this mode.
-option
: Toggle command-line option -option.
h
: Help.
more idiomatic version of the same, using the flip-flop-operator; also printing lines with '//'-style comments
This is the best way I have found to search out an application when I am not sure the title.
Grep is just to remove anything that does not contain the term in the title or short description (lots of things might include the search term in the description, such as libraries used by the application)
This is a naive way of finding source code comments in source code files that use C-like comments: // and /*...*/
Inspired by: http://www.commandlinefu.com/commands/view/8744/search-google-on-os-x
#!/bin/bash
if [ -n "$1" ]
then
firefox 'http://www.google.com/search?q="'$1'"'
else
firefox 'http://www.google.com'
fi
Ive aliased this script as 'google' on my system and I can type 'google "search terms"' to open firefox with my search terms. My first post here, if there are any improvements to be made please let me know in the comments.
Syntax:
google query_with_spaces "
so, make sure to end your query with a double quote
Yep, now you can finally google from the command line!
Here's a readable version "for your pleasure"(c):
google() { # search the web using google from the commandline
# syntax: google google
query=$(echo "$*" | sed "s:%:%25:g;s:&:%26:g;s:+:%2b:g;s:;:%3b:g;s: :+:g")
data=$(wget -qO - "https://ajax.googleapis.com/ajax/services/search/web?v=1.0&q=$query")
title=$(echo "$data" | tr '}' '\n' | sed "s/.*,\"titleNoFormatting//;s/\":\"//;s/\",.*//;s/\\u0026/'/g;s/\\\//g;s/#39\;//g;s/'amp;/\&/g" | head -1)
url="$(echo "$data" | tr '}' '\n' | sed 's/.*"url":"//;s/".*//' | head -1)"
echo "${title}: ${url} | http://www.google.com/search?q=${query}"
}
Enjoy :)
* Add comment with # in your command
* Later you can search that command on that comment with CTRL+R
In the title command, you could search it later by invoking the command search tool by first typing CTRL+R and then typing "revert"
You can install filterous with
sudo apt-get install libxslt1-dev; sudo easy_install -U filterous
Use find to recursively make a list of all files from the current directory and downwards. The files have to have an extension of the ones listed. Then for every file found, grep it for 'searchString', returns the filename if searchString is found.