All commands (13,536)
-
Instead of using clipboard register after opening vim we can use this command in order to edit clipboard content. For those who already have "xclip -i -selection clipboard -o" aliased to pbpaste it is yet more simple, just: alias vcb='pbpaste | vim -'
0alias vcb='xclip -i -selection clipboard -o | vim -' -
0bzip2recover damaged_file_name
-
install json-to-js as a npm global package
0cat data.json | json-to-js | pbcopy -
Requires installing yq (pip install yq)
0yq . -y <example.json -
This command will find all occurrences of one or more patterns in a collection of files and will delete every line matching the patterns in every file
1for file in $(egrep 'abc|def' *.sql | cut -d":" -f1 | uniq); do sed -i '/abc/d' ./$file ; sed -i '/def/d' ./$file; done -
This coloured prompt will show: username in green, grey "@" sign, hostname in red, current directory in yellow, typed commands in green.
1export PS1="\e[1;32m\u\e[0m@\e[1;31m\h\e[0m\e[1;33m\w:#> \e[1;32m" -
As an alternative to the above command, this one ditches the unnecessary and complicated for loop in favor of a way faster multi-core approach for a task that's more CPU than I/O intensive, making it a perfect suite for GNU parallel
2parallel cwebp -q 80 {} -o {.}.webp ::: *.png -
You could have that little benchmark run on all cores in parallel, as a multi-core benchmark or stress test First find the number of cores, then have parallel iterate over that in, well, parallel Show Sample Output
0time cat /proc/cpuinfo |grep proc|wc -l|xargs seq|parallel -N 0 echo "2^2^20" '|' bc -
Broken in two parts, first get the number of cores with cat /proc/cpuinfo |grep proc|wc -l and create a integer sequence with that number (xargs seq), then have GNU parallel loop that many times over the given command. Cheers! Show Sample Output
0time cat /proc/cpuinfo |grep proc|wc -l|xargs seq|parallel -N 0 echo "scale=4000\; a\(1\)\*4" '|' bc -l -
1find <folder> -type f -exec sed -i 's/my big String/newString/g' {} +
-
Get the running Kernel and Install date
1uname -a;rpm -qi "kernel"-`uname -r`|grep "Install" -
needs cwebp
0pngwebp(){ arg1=$1 for i in *.png; do name=`echo "${i%.*}"`; echo $name; cwebp -q $1 "${i}" -o "${name}.webp" done } -
1find "$(pwd)" -name "file-pattern*.gz" -exec zgrep -H 'pattern' {} \;
-
1grep --color -E 'pattern|' file
-
Fill the entire terminal screen. Is COLUMNS or LINES are undefined run "resize"
3yes "\\__/ " | tr "\n" " " | fold -$((($COLUMNS-3)/6*6+3)) | head -$LINES -
slighty shorter
1watch -c "netstat -nt | awk 'FNR > 3 {print \$6}' | sort | uniq -c" -
1$ watch -c "netstat -natp 2>/dev/null | tail -n +3 | awk '{print \$6}' | sort | uniq -c"
-
rename is a really powerfull to, as its name suggests, rename files Show Sample Output
2rename 'y/A-Z/a-z/' * -
0for f in `find`; do mv -v "$f" "`echo $f | tr '[A-Z]' '[a-z]'`"; done
-
This is a correction to https://www.commandlinefu.com/commands/view/22134 Use `-name` instead of `-iname`, because case-sensitivity is probably important when we're dealing with filenames. It's true that extensions are often capitalised (e.g., "something.JPG"), so choose whatever's appropriate. However, what is appropriate is the quoting of the name pattern, so the shell doesn't expand it incorrectly. Finally, `-delete` is clearer.
1find / -name "*.jpg" -delete -
# for description type man seq Show Sample Output
0seq 12 -
tput setaf 1 && tput rev && seq -ws "___|" 81|fold -69|tr "0-9" "_" && tput sgr0# (brick wall)6seq -ws "\\__/" 99|fold -69|tr "0-9" " " -
2seq -s " \\_/" 256|tr -d "0-9"|fold -70
-
Replace the underscore with any other character. e.g. + or - or =
2printf "%`tput cols`s"|sed "s/ /_/g" -
2echo boo{,,,,,,,,,,}
- 1 2 3 > Last ›
Considering A New Car?
You should consider a Tesla. Get 6 Months Free Supercharging.
Free SuperchargingWhat's this?
commandlinefu.com 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.
Check These Out
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.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10 - 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:
- » all commands
- » commands with 3 up-votes (commandlinefu3)
- » commands with 10 up-votes (commandlinefu10)