cmdfu(){ local TCF="/var/tmp/cmdfu"; echo " Searching..."; curl "$(echo "$@" | sed 's/ /-/g')/$(echo -n $@ | base64)/plaintext" --silent > "$TCF"; vim -c "set filetype=sh" -RM "$TCF"; rm "$TCF"; }

Search and display with VIMs syntax highlighting!

Multi-argument version, but with VIM loveliness :D

2011-12-06 10:01:27

These Might Interest You

  • When searching in vi, the search string gets highlighted but the highlighting can become a nuisance. By searching for the very unlikely pattern "^~" the highlighting is effectively switched off. Show Sample Output

    mpb · 2012-08-02 21:10:23 7
  • There's probably a more efficient way to do this rather than the relatively long perl program, but perl is my hammer, so text processing looks like a nail. This is of course a lot to type all at once. You can make it better by putting this somewhere: clf () { (curl -d "q=$@" 2>/dev/null) | egrep 'autocomplete|votes|destination' | perl -pi -e 's/<a style="display:none" class="destination" href="//g;s/<[^>]*>//g;s/">$/\n\n/g;s/^ +|\([0-9]+ votes,//g;s/^\//http:\/\/\//g'; } Then, to look up any command, you can do this: clf diff This is similar to except that it's just one line, so more in the spirit of CLF, in my opinion. Show Sample Output

    (curl -d q=grep | egrep 'autocomplete|votes|destination' | perl -pi -e 's/a style="display:none" class="destination" href="//g;s/<[^>]*>//g;s/">$/\n\n/g;s/^ +//g;s/^\//http:\/\/\//g'
    isaacs · 2009-07-08 22:10:49 4
  • This is a simple bash function and a key binding that uses commandlinefu's simple and easy search API. It prompts for a search term, then it uses curl to search commandline fu, and highlights the search results with less.

    function ds { echo -n "search : "; read ST; EST=`php -r "echo rawurlencode('$ST');"`; B64=`echo -n $ST| openssl enc -base64`; curl -s "$EST/$B64/plaintext" | less -p "$ST"; } ; bind '"\C-k"':"\"ds\C-m\""
    cparker · 2011-02-20 23:46:16 0
  • Here is the full function (got trunctated), which is much better and works for multiple queries. function cmdfu () { local t=~/cmdfu; until [[ -z $1 ]]; do echo -e "\n# $1 {{{1" >> $t; curl -s "$1/`echo -n $1|base64`/plaintext" | sed '1,2d;s/^#.*/& {{{2/g' | tee -a $t > $t.c; sed -i "s/^# $1 {/# $1 - `grep -c '^#' $t.c` {/" $t; shift; done; vim -u /dev/null -c "set ft=sh fdm=marker fdl=1 noswf" -M $t; rm $t $t.c } Searches commandlinefu for single/multiple queries and displays syntax-highlighted, folded, and numbered results in vim. Show Sample Output

    cmdfu(){ local t=~/cmdfu;echo -e "\n# $1 {{{1">>$t;curl -s "$1/`echo -n $1|base64`/plaintext"|sed '1,2d;s/^#.*/& {{{2/g'>$t;vim -u /dev/null -c "set ft=sh fdm=marker fdl=1 noswf" -M $t;rm $t; }
    AskApache · 2012-02-21 05:43:16 6
  • Search for one/many words on commandlinefu, results in vim for easy copy, manipulation. The -R flag is for readonly can still write to a file, but vim won't prompt for save on quit. What I'd really like is a way to do this from within vim in a new tab. Something like :Tex path/to/file but :cmdfu search terms

    cmdfu(){ curl "$(echo "$@" | sed 's/ /-/g')/$(echo -n $@ | base64)/plaintext" --silent | vim -R - }
    MeanderingCode · 2012-02-10 16:26:47 0

  • 1
    a2ps -R --columns=1 -M A4 -o - |lpr
    lionping · 2010-07-18 23:11:56 1

What Others Think

cmdfu(){ local c l=`builtin printf %${2:-${COLUMNS:-80}}s` TCF="${TMPDIR:-~/}/cmdfu"; until [[ -z ${1:-} ]]; do c=0; echo -e "\n\n\n# $1 {{{1\n#${l// /=}" >> $TCF; curl -s "$1/`echo -n $1|base64`/plaintext" | tee -a "$TCF.c" | sed '1d;s/^#.*/& {{{2/g' >> "$TCF"; c=`grep -c '^#' $TCF.c`; rm "$TCF.c"; sed -i "s/^# ${1} /# ${1} - ${c} /" $TCF; shift; done; vim -c "set filetype=sh foldmethod=marker foldlevel=1 nobackup" -RM "$TCF"; rm "$TCF"; }
AskApache · 325 weeks and 6 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. 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.

Share Your Commands

Stay in the loop…

Follow the Tweets.

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.


Subscribe to the feeds.

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: