ChatGPT解决这个技术问题 Extra ChatGPT

Assigning default values to shell variables with a single command in bash

I have a whole bunch of tests on variables in a bash (3.00) shell script where if the variable is not set, then it assigns a default, e.g.:

if [ -z "${VARIABLE}" ]; then 
    FOO='default'
else 
    FOO=${VARIABLE}
fi

I seem to recall there's some syntax to doing this in one line, something resembling a ternary operator, e.g.:

FOO=${ ${VARIABLE} : 'default' }

(though I know that won't work...)

Am I crazy, or does something like that exist?

Shell Parameter Expansion section of the bash shell reference is a good starting places: tiswww.case.edu/php/chet/bash/bashref.html#Shell-Expansions.
Gnu.org documentation for Shell Parameter Expansion (hint: there's a lot of other cool stuff you can do!)

M
Matthias Braun

Very close to what you posted, actually. You can use something called Bash parameter expansion to accomplish this.

To get the assigned value, or default if it's missing:

FOO="${VARIABLE:-default}"  # If variable not set or null, use default.
# If VARIABLE was unset or null, it still is after this (no assignment done).

Or to assign default to VARIABLE at the same time:

FOO="${VARIABLE:=default}"  # If variable not set or null, set it to default.

If I wanted to find this in the documentation, what would a google for? Googling with special characters like ${:-} isn't very easy.
In response to solarmist: "bash variable assignment default" let me to this page, and searching bash's manual page with 'variable ass' got me to the right section after ~five 'next'
Note that it's not bash-specific and will work with the whole shell-family. It's safe for generic-scripts.
@solarmist The key word is "bash parameter expansion", if you want to find more about it and its companions.
Here's a more in-depth explanation on the topic unix.stackexchange.com/a/122848/2407
H
Hans Ginzel

For command line arguments:

VARIABLE="${1:-$DEFAULTVALUE}"

which assigns to VARIABLE the value of the 1st argument passed to the script or the value of DEFAULTVALUE if no such argument was passed. Quoting prevents globbing and word splitting.


D
David Cook

If the variable is same, then

: "${VARIABLE:=DEFAULT_VALUE}"

assigns DEFAULT_VALUE to VARIABLE if not defined.

The colon builtin (:) ensures the variable result is not executed

The double quotes (") prevent globbing and word splitting.

Also see Section 3.5.3, Shell Parameter Expansion, in the Bash manual.


This tricky trick wasn't obvious to me, using the : no-effect builtin to eat the expansion of the ${..} BUT leaving VARIABLE set. Until now I was doing this: VARIABLE="${VARIABLE:-DEFAULT_VALUE}" and feeling dorky for using VARIABLE twice.
It turns out THIS DOES NOT ALWAYS WORK FOR BASH-BUILTIN VARIABLES. It's very very weird. Currently those known to me are HISTTIMEFORMAT
how would I set multiple default values? I tried ": ${VARIABLE:=DEFAULT_VALUE} : ${VARIABLE2:=DEFAULT_VALUE2}" but that doesnt seem to work...
@Hans: The colon is the command (which does nothing) and thus is needed only once. E.g. : ${FOO:=DEFAULT1} ${BAR:=DEFAULT2}
Any chance to use something like this with export? I want to make this variable available to the scripts called from the current script.
P
Pierre-Antoine Guillaume

To answer your question and on all variable substitutions

echo "${var}"
echo "Substitute the value of var."
    

echo "${var:-word}"
echo "If var is null or unset, word is substituted for var. The value of var does not change."
    

echo "${var:=word}"
echo "If var is null or unset, var is set to the value of word."
    

echo "${var:?message}"
echo "If var is null or unset, message is printed to standard error. This checks that variables are set correctly."
    

echo "${var:+word}"
echo "If var is set, word is substituted for var. The value of var does not change."

You can escape the whole expression by putting a \ between the dollar sign and the rest of the expression.

echo "$\{var}"

There's also {var-default} where default will be used only when var is undefined. If var is defined but null, default won't be used.
Why is there a a backslash in each line? Other answers don't have it.
M
Montells

Even you can use like default value the value of another variable

having a file defvalue.sh

#!/bin/bash
variable1=$1
variable2=${2:-$variable1}

echo $variable1
echo $variable2

run ./defvalue.sh first-value second-value output

first-value
second-value

and run ./defvalue.sh first-value output

first-value
first-value

C
Clément

see here under 3.5.3(shell parameter expansion)

so in your case

${VARIABLE:-default}

C
Curtis Mattoon

FWIW, you can provide an error message like so:

USERNAME=${1:?"Specify a username"}

This displays a message like this and exits with code 1:

./myscript.sh
./myscript.sh: line 2: 1: Specify a username

A more complete example of everything:

#!/bin/bash
ACTION=${1:?"Specify 'action' as argv[1]"}
DIRNAME=${2:-$PWD}
OUTPUT_DIR=${3:-${HOMEDIR:-"/tmp"}}

echo "$ACTION"
echo "$DIRNAME"
echo "$OUTPUT_DIR"

Output:

$ ./script.sh foo
foo
/path/to/pwd
/tmp

$ export HOMEDIR=/home/myuser
$ ./script.sh foo
foo
/path/to/pwd
/home/myuser

$ACTION takes the value of the first argument, and exits if empty

$DIRNAME is the 2nd argument, and defaults to the current directory

$OUTPUT_DIR is the 3rd argument, or $HOMEDIR (if defined), else, /tmp. This works on OS X, but I'm not positive that it's portable.


R
Rob Wells

Then there's the way of expressing your 'if' construct more tersely:

FOO='default'
[ -n "${VARIABLE}" ] && FOO=${VARIABLE}

A
Assaf Shomer

Here is an example

#!/bin/bash

default='default_value'
value=${1:-$default}

echo "value: [$value]"

save this as script.sh and make it executable. run it without params

./script.sh
> value: [default_value]

run it with param

./script.sh my_value
> value: [my_value]

I
InsOp

It is possible to chain default values like so:

DOCKER_LABEL=${GIT_TAG:-${GIT_COMMIT_AND_DATE:-latest}}

i.e. if $GIT_TAG doesnt exist, take $GIT_COMMIT_AND_DATE - if this doesnt exist, take "latest"