Convert a script to one-liner

(sed 's/#.*//g'|sed '/^ *$/d'|tr '\n' ';'|xargs echo) <
Opposite: Convert an one-liner to script: foo() { <one-liner> ; } ... typeset -f foo ... unset -f foo

By: knoppix5
2013-10-26 23:23:51

These Might Interest You

  • (Please see sample output for usage) script.bash is your script, which will be crypted to script.bash --> You can execute only if you know the password. If you die, your script dies with you. If you modify the startup line, be careful with the offset calculation of the crypted block (the XX string). Not difficult to make script editable (an offset-dd piped to a gpg -d piped to a vim - piped to a gpg -c directed to ), but not enough space to do it on a one liner. Show Sample Output

    echo "eval \"\$(dd if=\$0 bs=1 skip=XX 2>/dev/null|gpg -d 2>/dev/null)\"; exit" >; sed -i s:XX:$(stat -c%s; gpg -c < script.bash >>; chmod +x
    rodolfoap · 2013-03-09 11:16:48 5
  • I often write a one-liner which I want to use later in a script. Show Sample Output

    declare -f <function name>
    RanyAlbeg · 2011-04-07 12:35:38 2
  • I have used crontab to run the one-liner and also to run a script containing the one-liner. Neither works. Show Sample Output

    20 11 * * * root /bin/top -n 2 -d 1 | grep "Cpu(s):" > file.txt
    robertdma · 2012-10-23 15:39:57 0
  • This one liner; combines all sequentially numbered files; in this example IMG_0001.png to IMG_1121.png by generating the shell script, making the shell script executable and then running the shell script to combine the 1121 png into a single png file named _final.png tested on Mac OS X 10.6.3 with ImageMagick 6.5.8-0 2009-11-22 Q16

    echo -n "convert " >; printf "IMG_%00004u.png " {1..1121} >>; echo -n "-layers merge _final.png" >>; chmod +x && ./
    IsraelTorres · 2010-05-22 03:56:30 0

What Others Think

What a fascinating idea :-) Unfortunately, it's easily confused. Many compound statements get unnecessary semi-colons: if [ "$x" = 1 ]; then; echo one; fi Also, one of my favourite shell variables gets chewed up: $# (the number of parameters).
flatcap · 242 weeks and 5 days ago
slightly improoved, yet far from perfect: (sed '/if *$\|then *$\|else *$/!s/$/;/g'|sed 's/^#.*;\| #.*;//g'|xargs echo) <
knoppix5 · 242 weeks and 4 days ago
I ended up with: (sed -e 's/^\s*\(.*\)\s*/\1/' -e 's/\([^$]\|^\)#.*//' -e '/^$/d' | paste -s -d\; | sed -e 's/\<\(then\|do\)\>;/\1 /g') < sed part 1: trim leading/trailing whitespace sed part 2: # at the beginning of a line, or # (but not preceded by $) sed part 3: delete empty lines paste: join lines with a ; sed part 4: replace 'then;' or 'do;' with 'then' or 'do' However, your 'xargs echo' is much nicer. (sed -e 's/\([^$]\|^\)#.*//' -e '/^$/d' | tr '\n' ';' | xargs echo | sed -e 's/\<\(then\|do\)\>;/\1/g') <
flatcap · 242 weeks and 4 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: