Revert merging the functions together. Silly me.

Instead, make it statically wrapped. Why not? Why call `fmt`! Trying to be
'cool'?
This commit is contained in:
Colin Shea 2011-11-27 03:28:13 -07:00
commit e584cf2f7d

View file

@ -1,10 +1,50 @@
# Contributed and SLIGHTLY modded by Matt Parnell/ilikenwf <parwok -at- gmail>
# Created by the blogger at the URL below...I don't know where to find his/her name
# Original found at http://www.shellperson.net/sprunge-pastebin-script/
#
# Modified by Evaryont to:
# - Detect syntax via pygments
# - Behave nicely as a plugin
usage() {
cat << HERE
DESCRIPTION
Upload data and fetch URL from the pastebin http://sprunge.us
USAGE
$0 filename.txt
$0 < filename.txt
piped_data | $0
INPUT METHODS
$0 can accept piped data, STDIN redirection [<filename.txt], text strings
following the command as arguments, or filenames as arguments. Only one
of these methods can be used at a time, so please see the note on
precedence. Also, note that using a pipe or STDIN redirection will treat
tabs as spaces, or disregard them entirely (if they appear at the
beginning of a line). So I suggest using a filename as an argument if
tabs are important either to the function or readability of the code.
PRECEDENCE
STDIN redirection has precedence, then piped input, then a filename as an
argument. Example:
echo piped | "$0" arguments.txt < stdin_redirection.txt
In this example, the contents of file_as_stdin_redirection.txt would be
uploaded. Both the piped_text and the file_as_argument.txt are ignored. If
there is piped input and arguments, the arguments will be ignored, and the
piped input uploaded.
FILENAMES
If a filename is misspelled or doesn't have the necessary path
description, it will NOT generate an error, but will instead treat it as
a text string and upload it.
HERE
#exit
return 0
}
sprunge() {
if [ -t 0 ]; then
@ -19,34 +59,7 @@ sprunge() {
url=$(cat "$*" | curl -F 'sprunge=<-' http://sprunge.us)
fi
else
cat << HERE
DESCRIPTION
Upload data and fetch URL from the pastebin http://sprunge.us
USAGE
$0 filename.txt
$0 < filename.txt
piped_data | $0
NOTES
--------------------------------------------------------------------------
* INPUT METHODS *
$0 can accept piped data, STDIN redirection [<filename.txt], text strings following the command as arguments, or filenames as arguments. Only one of these methods can be used at a time, so please see the note on precedence. Also, note that using a pipe or STDIN redirection will treat tabs as spaces, or disregard them entirely (if they appear at the beginning of a line). So I suggest using a filename as an argument if tabs are important either to the function or readability of the code.
* PRECEDENCE *
STDIN redirection has precedence, then piped input, then a filename as an argument.
EXAMPLE:
echo piped | "$0" arguments.txt < stdin_redirection.txt
In this example, the contents of file_as_stdin_redirection.txt would be uploaded. Both the piped_text and the file_as_argument.txt are ignored. If there is piped input and arguments, the arguments will be ignored, and the piped input uploaded.
* FILENAMES *
If a filename is misspelled or doesn't have the necessary path description, it will NOT generate an error, but will instead treat it as a text string and upload it.
--------------------------------------------------------------------------
HERE | fmt -s >&2
return 0
usage
fi
else
syntax="text" # We're dumb in this mode. So, dumb syntax highlighting!