Commands by jlaunay (16)
-
-3sed 's/#.*//' /etc/fstab | column -t
-
0sudo file -bs /dev/sda | sed -e 's/.*partition 1\(.*\) code offset.*/partition 1\1/g' -e 's/\(.\);/\1\n/g'
-
Define a git alias then git dcolor
3git config alias.dcolor "diff --color-words" -
5file=<filename>;vim ${file} -e -s -c 'runtime! syntax/syntax.vim' -c 'runtime! syntax/2html.vim' -c "w ${file}.html" -c 'q!' -c 'q!' > /dev/null
-
Use sed to color the output of a human-readable dmesg output
21dmesg -T|sed -e 's|\(^.*'`date +%Y`']\)\(.*\)|\x1b[0;34m\1\x1b[0m - \2|g' -
3dig myip.opendns.com @Resolver1.opendns.com +short
-
This command give a human readable result without messing up the sorting.
1for i in G M K; do du -hx /var/ | grep [0-9]$i | sort -nr -k 1; done | less -
As cp is often an alias to cp -i you can use \cp (or cp full path /bin/cp) to use the real cp command instead of its alias
-1cp -rf srcdir/* destdir -
Using xargs is usually much quicker as it does not have to execute chmod for every file
-2find . -type f -print0 | xargs -0 chmod a-x -
-2watch -n 1 "awk 'NR==3 {print \"Signal strength = \" \$3 \"00 %\"}''' /proc/net/wireless"
-
-RR option is used to resume the first appropriate detached screen session
2screen -RR -
0sudo dmidecode -s system-product-name
-
or add this line to your ~/.vimrc if using vim
0:autocmd BufNewFile *.sh,*.bash 0put =\"#!/bin/bash\<nl># -*- coding: UTF8 -*-\<nl>\<nl>\"|$ -
as suggest in frans coment : '/^#[^!].*/d' -> remove if line begin with # except shebang #!/bin/bash 's/\(.*[^!]\)#.*[^}]/\1/' -> remove inline comments except shebang and ${variable#}
0sed -i -e '/^#[^!].*/d' -e 's/\(.*[^!]\)#.*[^}]/\1/' <filename> -
1sed -i <start>,<end>d <filename>
-
a : to keep files permissions --no-whole file : use rsync?s delta-transfer algorithm --inplace : writes the updated data directly to the destination file optionnal -> add --remove-source-files to mv instead of cp
0rsync -aP --no-whole-file --inplace
What'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)
- » commands by jlaunay