How variables inside braces are evaluated












5















I'm new to shell scripting and I came across these expressions



${var:-val} and ${var-val}



${var:+val} and ${var+val}



${var:=val} and ${var=val}



so how are they evaluated and what are the differences between them






bash shell scripting







share|improve this question




















  • 3





    IMO, not a duplicate. the linked answer only answers 1/3 of this question.

    – cas
    May 30 '16 at 3:06











  • What linked answer?

    – fpmurphy
    May 30 '16 at 9:25











  • @fpmurphy1 What does :- mean in a shell script.

    – Stephen Kitt
    May 30 '16 at 9:31
















5















I'm new to shell scripting and I came across these expressions



${var:-val} and ${var-val}



${var:+val} and ${var+val}



${var:=val} and ${var=val}



so how are they evaluated and what are the differences between them






bash shell scripting







share|improve this question




















  • 3





    IMO, not a duplicate. the linked answer only answers 1/3 of this question.

    – cas
    May 30 '16 at 3:06











  • What linked answer?

    – fpmurphy
    May 30 '16 at 9:25











  • @fpmurphy1 What does :- mean in a shell script.

    – Stephen Kitt
    May 30 '16 at 9:31














5












5








5


2






I'm new to shell scripting and I came across these expressions



${var:-val} and ${var-val}



${var:+val} and ${var+val}



${var:=val} and ${var=val}



so how are they evaluated and what are the differences between them






bash shell scripting







share|improve this question
















I'm new to shell scripting and I came across these expressions



${var:-val} and ${var-val}



${var:+val} and ${var+val}



${var:=val} and ${var=val}



so how are they evaluated and what are the differences between them






bash shell scripting




bash shell scripting






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 44 mins ago









Rui F Ribeiro

40.1k1479136




40.1k1479136










asked May 29 '16 at 21:39









WLIONWLION

1553




1553








  • 3





    IMO, not a duplicate. the linked answer only answers 1/3 of this question.

    – cas
    May 30 '16 at 3:06











  • What linked answer?

    – fpmurphy
    May 30 '16 at 9:25











  • @fpmurphy1 What does :- mean in a shell script.

    – Stephen Kitt
    May 30 '16 at 9:31














  • 3





    IMO, not a duplicate. the linked answer only answers 1/3 of this question.

    – cas
    May 30 '16 at 3:06











  • What linked answer?

    – fpmurphy
    May 30 '16 at 9:25











  • @fpmurphy1 What does :- mean in a shell script.

    – Stephen Kitt
    May 30 '16 at 9:31








3




3





IMO, not a duplicate. the linked answer only answers 1/3 of this question.

– cas
May 30 '16 at 3:06





IMO, not a duplicate. the linked answer only answers 1/3 of this question.

– cas
May 30 '16 at 3:06













What linked answer?

– fpmurphy
May 30 '16 at 9:25





What linked answer?

– fpmurphy
May 30 '16 at 9:25













@fpmurphy1 What does :- mean in a shell script.

– Stephen Kitt
May 30 '16 at 9:31





@fpmurphy1 What does :- mean in a shell script.

– Stephen Kitt
May 30 '16 at 9:31










1 Answer
1






active

oldest

votes


















6














These are all various forms of parameter expansion with alternatives:





  • ${var:-val} is replaced by val if var is unset or null, ${var} otherwise (so val is a "default value");


  • ${var:=val} first assigns val to var if var is unset or null, and then (in all cases) is replaced by ${var};


  • ${var:+val} is replaced with nothing if var is unset or null, val otherwise.


Omitting the : drops the "or null" part of all these definitions.



This is all described in the bash(1) manpage.



Some examples might help:



unset a

echo "${a:-default}"


produces default, as does echo "${a-default}".



a=

echo "${a:-default}"


again produces default, but echo "${a-default}" outputs a blank line.



a=test

echo "${a:-default}"


produces test, as does echo "${a-default}".



unset a

echo "${a:=default}"


produces default, and a is now default (as confirmed by echo "${a}").



The + form might seem strange, but it is useful when constructing variables in several steps:



PATH="${PATH}${PATH:+:}/blah/bin"


will add : before /blah/bin only if PATH is non-empty, which avoids having a path starting with :.






share|improve this answer


























  • The :+ form is also useful for avoiding placing the empty string as an argument on a command line, while still properly double-quoting the variable. e.g. grep ${ignorecase:+"$ignorecase"} ... . The other, worse, alternative is to just use $ignorecase unquoted on the cmd line...which is only safe if you know exactly what $ignorecase can contain.

    – cas
    May 30 '16 at 12:47













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f286335%2fhow-variables-inside-braces-are-evaluated%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









6














These are all various forms of parameter expansion with alternatives:





  • ${var:-val} is replaced by val if var is unset or null, ${var} otherwise (so val is a "default value");


  • ${var:=val} first assigns val to var if var is unset or null, and then (in all cases) is replaced by ${var};


  • ${var:+val} is replaced with nothing if var is unset or null, val otherwise.


Omitting the : drops the "or null" part of all these definitions.



This is all described in the bash(1) manpage.



Some examples might help:



unset a

echo "${a:-default}"


produces default, as does echo "${a-default}".



a=

echo "${a:-default}"


again produces default, but echo "${a-default}" outputs a blank line.



a=test

echo "${a:-default}"


produces test, as does echo "${a-default}".



unset a

echo "${a:=default}"


produces default, and a is now default (as confirmed by echo "${a}").



The + form might seem strange, but it is useful when constructing variables in several steps:



PATH="${PATH}${PATH:+:}/blah/bin"


will add : before /blah/bin only if PATH is non-empty, which avoids having a path starting with :.






share|improve this answer


























  • The :+ form is also useful for avoiding placing the empty string as an argument on a command line, while still properly double-quoting the variable. e.g. grep ${ignorecase:+"$ignorecase"} ... . The other, worse, alternative is to just use $ignorecase unquoted on the cmd line...which is only safe if you know exactly what $ignorecase can contain.

    – cas
    May 30 '16 at 12:47


















6














These are all various forms of parameter expansion with alternatives:





  • ${var:-val} is replaced by val if var is unset or null, ${var} otherwise (so val is a "default value");


  • ${var:=val} first assigns val to var if var is unset or null, and then (in all cases) is replaced by ${var};


  • ${var:+val} is replaced with nothing if var is unset or null, val otherwise.


Omitting the : drops the "or null" part of all these definitions.



This is all described in the bash(1) manpage.



Some examples might help:



unset a

echo "${a:-default}"


produces default, as does echo "${a-default}".



a=

echo "${a:-default}"


again produces default, but echo "${a-default}" outputs a blank line.



a=test

echo "${a:-default}"


produces test, as does echo "${a-default}".



unset a

echo "${a:=default}"


produces default, and a is now default (as confirmed by echo "${a}").



The + form might seem strange, but it is useful when constructing variables in several steps:



PATH="${PATH}${PATH:+:}/blah/bin"


will add : before /blah/bin only if PATH is non-empty, which avoids having a path starting with :.






share|improve this answer


























  • The :+ form is also useful for avoiding placing the empty string as an argument on a command line, while still properly double-quoting the variable. e.g. grep ${ignorecase:+"$ignorecase"} ... . The other, worse, alternative is to just use $ignorecase unquoted on the cmd line...which is only safe if you know exactly what $ignorecase can contain.

    – cas
    May 30 '16 at 12:47
















6












6








6







These are all various forms of parameter expansion with alternatives:





  • ${var:-val} is replaced by val if var is unset or null, ${var} otherwise (so val is a "default value");


  • ${var:=val} first assigns val to var if var is unset or null, and then (in all cases) is replaced by ${var};


  • ${var:+val} is replaced with nothing if var is unset or null, val otherwise.


Omitting the : drops the "or null" part of all these definitions.



This is all described in the bash(1) manpage.



Some examples might help:



unset a

echo "${a:-default}"


produces default, as does echo "${a-default}".



a=

echo "${a:-default}"


again produces default, but echo "${a-default}" outputs a blank line.



a=test

echo "${a:-default}"


produces test, as does echo "${a-default}".



unset a

echo "${a:=default}"


produces default, and a is now default (as confirmed by echo "${a}").



The + form might seem strange, but it is useful when constructing variables in several steps:



PATH="${PATH}${PATH:+:}/blah/bin"


will add : before /blah/bin only if PATH is non-empty, which avoids having a path starting with :.






share|improve this answer















These are all various forms of parameter expansion with alternatives:





  • ${var:-val} is replaced by val if var is unset or null, ${var} otherwise (so val is a "default value");


  • ${var:=val} first assigns val to var if var is unset or null, and then (in all cases) is replaced by ${var};


  • ${var:+val} is replaced with nothing if var is unset or null, val otherwise.


Omitting the : drops the "or null" part of all these definitions.



This is all described in the bash(1) manpage.



Some examples might help:



unset a

echo "${a:-default}"


produces default, as does echo "${a-default}".



a=

echo "${a:-default}"


again produces default, but echo "${a-default}" outputs a blank line.



a=test

echo "${a:-default}"


produces test, as does echo "${a-default}".



unset a

echo "${a:=default}"


produces default, and a is now default (as confirmed by echo "${a}").



The + form might seem strange, but it is useful when constructing variables in several steps:



PATH="${PATH}${PATH:+:}/blah/bin"


will add : before /blah/bin only if PATH is non-empty, which avoids having a path starting with :.







share|improve this answer














share|improve this answer



share|improve this answer








edited May 30 '16 at 9:33

























answered May 30 '16 at 9:26









Stephen KittStephen Kitt

171k24386462




171k24386462













  • The :+ form is also useful for avoiding placing the empty string as an argument on a command line, while still properly double-quoting the variable. e.g. grep ${ignorecase:+"$ignorecase"} ... . The other, worse, alternative is to just use $ignorecase unquoted on the cmd line...which is only safe if you know exactly what $ignorecase can contain.

    – cas
    May 30 '16 at 12:47





















  • The :+ form is also useful for avoiding placing the empty string as an argument on a command line, while still properly double-quoting the variable. e.g. grep ${ignorecase:+"$ignorecase"} ... . The other, worse, alternative is to just use $ignorecase unquoted on the cmd line...which is only safe if you know exactly what $ignorecase can contain.

    – cas
    May 30 '16 at 12:47



















The :+ form is also useful for avoiding placing the empty string as an argument on a command line, while still properly double-quoting the variable. e.g. grep ${ignorecase:+"$ignorecase"} ... . The other, worse, alternative is to just use $ignorecase unquoted on the cmd line...which is only safe if you know exactly what $ignorecase can contain.

– cas
May 30 '16 at 12:47







The :+ form is also useful for avoiding placing the empty string as an argument on a command line, while still properly double-quoting the variable. e.g. grep ${ignorecase:+"$ignorecase"} ... . The other, worse, alternative is to just use $ignorecase unquoted on the cmd line...which is only safe if you know exactly what $ignorecase can contain.

– cas
May 30 '16 at 12:47




















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f286335%2fhow-variables-inside-braces-are-evaluated%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Loup dans la culture

Image
Loups sur une enluminure du Bestiaire d'Aberdeen Le loup est l'animal le plus emblématique de l'histoire de l'Eurasie, il était à l'honneur durant l'Antiquité chez la totalité des anciens peuples européens [ 1 ] . Sommaire 1 Le loup dans la mythologie 2 Les loups dans le folklore 2.1 L'évolution des mentalités 2.2 Le loup dans la psychanalyse 3 Le loup dans les œuvres culturelles 3.1 Le loup dans la littérature 3.1.1 Fables 3.1.2 Poésie 3.1.3 Romans 3.1.4 Littérature jeunesse 3.1.4.1 Quelques titres d'albums contemporains 3.1.5 Bande dessinée 3.2 Le loup à l'écran 3.2.1 Le cinéma et la télévision 3.2.2 Documentaires 3.2.3 Dessins animés 3.2.4 Jeux vidéo 3.3 Le loup en peinture et en sculpture 3.4 Le loup dans les œuvres musicales 4 Le loup et les noms propres 5 Bibliographie 6 Notes et références 7 Voir aussi 7.1 Articles connexes
Read more

How to solve the problem of ntp “Unable to contact time server” from KDE?

Image
1 0 I want to set date and time automatically but this error appears when I try to .. I'm using openSUSE, I tried different servers but it didn't work either, help please! It doesn't seem to be a network problem: $ ping pool.ntp.org 64 bytes from 41.78.128.17: icmp_seq=1 ttl=41 time=260 ms To the question of whether ntpd is installed and running: $ ps -C ntpd PID TTY TIME CMD i.e. there's no ntpd process running. $ rpm -qa | grep ntp yast2-ntp-client-3.1.12-1.7.noarch ntp-4.2.6p5-25.2.1.i586 Further information from the comments: $ sudo ntpdate pool.ntp.org 25 Sep 19:41:51 ntpdate[3162]: no server suitable for synchronization found networking kde opensuse ntp ntpd sh
Read more

ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux

Image
0 1 I have an ASUS Zenbook UX433,on which ASUS decided to innovate by embedding a Numpad inside the touchpad (see picture 1). Toggling between classic touchpad mode and numpad (also turns the touchpad LEDs on) can be done through the golden button in the top-right corner of the touchpad. However, on my Manjaro arch Linux config, this behavior does not work by default and I can only use the touchpad, no numpad. Has anyone been able to configure the numpad to work on Linux, or have any idea how this could be achieved? EDIT1: I have had a look at the official Windows drivers for the UX433FA TouchPad, but was not able to make anything of it. I tried installing them on Linux using tools like NDISWrapper, but they do not detect the TouchPad/Numpad hardware, and my understanding of drivers is too limited.
Read more