Bash Processing of Command Line Parameters that Include Spaces: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 41: Line 41:
#
#
IFS=${separator}
IFS=${separator}
set ${args}
set - ${args}
IFS="$(printf ' \t\n')" # restore the standard separators
IFS="$(printf ' \t\n')" # restore the standard separators



Revision as of 01:13, 24 September 2017

Internal

Overview

This page documents a coding pattern to be used when some of the command line parameters need to be processed in the wrapper shell script, and the rest of the parameter, that may include spaces, need to be passed unchanged to the target process. The pattern uses a special separator character, that is injected between the arguments to be passed to the lower layer, followed by the recreation of the command line with set.

Double-quote enclosed and single-quote encloses command line arguments that contain spaces are consistently handled.

# ...

local args
local separator=$'\x1f' # US - unit separator

while [ -n "$1" ]; do

    if [ "$1" = "..." ]; then

        #
        # process arguments that make sense at this layer
        #
        echo "processing $1 at this level ..."

        # ...

    else

        #
        # ... and accumulate the rest of the arguments between special separator characters
        #
        [ -z "${args}" ] && args="$1" || args="${args}${separator}$1"
    fi
    shift
done

#
# re-assemble the command line, by re-initializing the positional parameters, and pass it to the underlying process
#
IFS=${separator}
set - ${args}
IFS="$(printf ' \t\n')" # restore the standard separators

#
# Use "$@" built-in variable, which encloses each positional parameter in its own set of double quotes
#

java -cp ... io.novaordis.playground.Main "$@"