Variable with quotation marks “$()” The 2019 Stack Overflow Developer Survey Results Are...
Is it okay to consider publishing in my first year of PhD?
Output the Arecibo Message
If my opponent casts Ultimate Price on my Phantasmal Bear, can I save it by casting Snap or Curfew?
How much of the clove should I use when using big garlic heads?
How can I add encounters in the Lost Mine of Phandelver campaign without giving PCs too much XP?
How can I have a shield and a way of attacking with a ranged weapon at the same time?
Why is this code so slow?
Are spiders unable to hurt humans, especially very small spiders?
Did Scotland spend $250,000 for the slogan "Welcome to Scotland"?
How did passengers keep warm on sail ships?
What information about me do stores get via my credit card?
Deal with toxic manager when you can't quit
Short story: child made less intelligent and less attractive
Match Roman Numerals
Getting crown tickets for Statue of Liberty
What is the meaning of Triage in Cybersec world?
Pokemon Turn Based battle (Python)
What could be the right powersource for 15 seconds lifespan disposable giant chainsaw?
Variable with quotation marks "$()"
How do I free up internal storage if I don't have any apps downloaded?
Can we generate random numbers using irrational numbers like π and e?
Can you cast a spell on someone in the Ethereal Plane, if you are on the Material Plane and have the True Seeing spell active?
What do these terms in Caesar's Gallic Wars mean?
A word that means fill it to the required quantity
Variable with quotation marks “$()”
The 2019 Stack Overflow Developer Survey Results Are InWhat is the point of the bash Null-operator “:”, colon?Why does bash remove n in $(cat file)?gdialog cannot output variablefind does not work with my variablebash variable array names and getting valuesDefining and incrementing a variable in bashRename directory using a variableFor loop with variable incrementusing variable within quotation marksQuotation Mark-InceptionUsing bash in combination with psql, passing variable between themAssigned variable for pipeline is not working
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
Previously a member @Evan Chen, wrote this script :
#!/bin/bash
while [ true ]
do
currentoutput="$(lsusb)"
if [ "$currentoutput" != "$lastoutput" ]
then
echo "" date and Time >> test.log
date +%x_r >> test.log
lastoutput="$(lsusb)"
lsusb >> test.log
fi
sleep 5
done
I'm a newbie, trying to learn fast and I got a question about the variable's quotation marks.
Put a variable between $(), I get it, but why the quotation marks are needed, even in the if statement ?
To make a nested command ??
Thanks
bash scripts
New contributor
add a comment |
Previously a member @Evan Chen, wrote this script :
#!/bin/bash
while [ true ]
do
currentoutput="$(lsusb)"
if [ "$currentoutput" != "$lastoutput" ]
then
echo "" date and Time >> test.log
date +%x_r >> test.log
lastoutput="$(lsusb)"
lsusb >> test.log
fi
sleep 5
done
I'm a newbie, trying to learn fast and I got a question about the variable's quotation marks.
Put a variable between $(), I get it, but why the quotation marks are needed, even in the if statement ?
To make a nested command ??
Thanks
bash scripts
New contributor
add a comment |
Previously a member @Evan Chen, wrote this script :
#!/bin/bash
while [ true ]
do
currentoutput="$(lsusb)"
if [ "$currentoutput" != "$lastoutput" ]
then
echo "" date and Time >> test.log
date +%x_r >> test.log
lastoutput="$(lsusb)"
lsusb >> test.log
fi
sleep 5
done
I'm a newbie, trying to learn fast and I got a question about the variable's quotation marks.
Put a variable between $(), I get it, but why the quotation marks are needed, even in the if statement ?
To make a nested command ??
Thanks
bash scripts
New contributor
Previously a member @Evan Chen, wrote this script :
#!/bin/bash
while [ true ]
do
currentoutput="$(lsusb)"
if [ "$currentoutput" != "$lastoutput" ]
then
echo "" date and Time >> test.log
date +%x_r >> test.log
lastoutput="$(lsusb)"
lsusb >> test.log
fi
sleep 5
done
I'm a newbie, trying to learn fast and I got a question about the variable's quotation marks.
Put a variable between $(), I get it, but why the quotation marks are needed, even in the if statement ?
To make a nested command ??
Thanks
bash scripts
bash scripts
New contributor
New contributor
edited 1 hour ago
Shankhara
New contributor
asked 1 hour ago
ShankharaShankhara
62
62
New contributor
New contributor
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
In currentoutput="$(lsusb)"
lsusb is not a variable, it is a command. What this statement does, it executes lsusb
command and assigns its output to currentoutput
variable.
Older syntax for this was
currentoutput=`lsusb`
you can find it in many examples and scripts
To answer the other part of your question, if [ ]
is just how syntax for if
is defined in bash. See more in https://www.tldp.org/LDP/Bash-Beginners-Guide/html/sect_07_01.html
add a comment |
The following runs the external command command
and returns its output.
"$(command)"
Without the brackets/parentheses, this would look for a variable instead of running a command:
"$variable"
As for the difference between $variable
and "$variable"
, this becomes relevant when $variable
contains spaces. When using "$variable"
, the entire variable contents will be inserted into a single string even if the contents include spaces. When using $variable
the contents of the variable may be expanded into an argument list of multiple arguments.
HI @thomasrutter, I'm sorry, i meant quotation mark ... I edit my comment now !
– Shankhara
1 hour ago
add a comment |
Quotation marks prevent word splitting - that is breaking down variables into multiple items at whitespaces (or to be more exact, at spaces, tabs, and newlines as defined in default value of $IFS
shell variable).
For example,
$ var="one two"
$ howmany(){ echo $#; }
$ howmany $var
2
$ howmany "$var"
1
Here we define howmany
function which just lets us know how many positional parameters are given. As you can see, there are two items being passed to the variable, and with the quotes the text in the variable is treated as one unit.
This is important for accurate passing of information. For example, if the variable contains path to file, and the filename contains spaces anywhere in the path, the command you are trying to run may fail or give inaccurate result. If we were trying to create file with $var
variable, touch $var
would create two files, but touch "$var"
just one.
Same goes for [ "$currentoutput" != "$lastoutput" ]
part. This particular test performs comparison on two strings. When the test runs, the [
command would need to see 3 arguments - a text string, the !=
operator, and another text string. Keeping double quotes prevents word splitting, and the [
commands sees exactly those 3 arguments. Now what happens if variables are unquoted ?
$ var="hello world"
$ foo="hi world"
$ [ $var != $foo ]
bash: [: too many arguments
$
Here, word splitting occurs, and instead [
sees two strings hello
and world
followed by !=
, followed by two other strings hi world
. Key point is that without double quotes, contents of variables are understood as separate units rather than one whole item.
Assigning command substitution doesn't require double quotes as in
var=$( df )
where you have df
command's output saved to var
. However, it is a good habit to always double quote variables and command substitution $(...)
unless you do in fact want the output to be treated as separate items.
On side note, the
while [ true ]
part can be
while true
[
is a command which evaluates its arguments, and [ whatever ]
is always true regardless of what is inside. By contrast, while true
uses the command true
which always returns success exit status (and that's exactly what while
loop needs). The difference is a bit more clarity and less testing performed. Alternatively, you could also use :
instead of true
The double quotes echo "" date and Time
part could probably be removed. They merely insert empty string and add extra space to the output. If that's desired, feel free to keep them there, but there's no particular functional value in this case.
lsusb >> test.log
This part could probably be replaced with echo "$currentoutput" >> test.log
. There's no reason to run lsusb
again after it has been ran already in currentoutput=$(lsusb)
. In cases where trailing newlines
have to be preserved in the output - one could see the value in running a command multiple times, but in case of lsusb
there's no need for that. The less external commands you call, the better, because every call to a non-built-in command costs in CPU, memory usage, and execution time ( even though the commands are probably pre-loaded from memory).
See also:
- When is double-quoting necessary?
- What is the point of the bash null operator : (colon)?
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});
}
});
Shankhara is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1133173%2fvariable-with-quotation-marks%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
In currentoutput="$(lsusb)"
lsusb is not a variable, it is a command. What this statement does, it executes lsusb
command and assigns its output to currentoutput
variable.
Older syntax for this was
currentoutput=`lsusb`
you can find it in many examples and scripts
To answer the other part of your question, if [ ]
is just how syntax for if
is defined in bash. See more in https://www.tldp.org/LDP/Bash-Beginners-Guide/html/sect_07_01.html
add a comment |
In currentoutput="$(lsusb)"
lsusb is not a variable, it is a command. What this statement does, it executes lsusb
command and assigns its output to currentoutput
variable.
Older syntax for this was
currentoutput=`lsusb`
you can find it in many examples and scripts
To answer the other part of your question, if [ ]
is just how syntax for if
is defined in bash. See more in https://www.tldp.org/LDP/Bash-Beginners-Guide/html/sect_07_01.html
add a comment |
In currentoutput="$(lsusb)"
lsusb is not a variable, it is a command. What this statement does, it executes lsusb
command and assigns its output to currentoutput
variable.
Older syntax for this was
currentoutput=`lsusb`
you can find it in many examples and scripts
To answer the other part of your question, if [ ]
is just how syntax for if
is defined in bash. See more in https://www.tldp.org/LDP/Bash-Beginners-Guide/html/sect_07_01.html
In currentoutput="$(lsusb)"
lsusb is not a variable, it is a command. What this statement does, it executes lsusb
command and assigns its output to currentoutput
variable.
Older syntax for this was
currentoutput=`lsusb`
you can find it in many examples and scripts
To answer the other part of your question, if [ ]
is just how syntax for if
is defined in bash. See more in https://www.tldp.org/LDP/Bash-Beginners-Guide/html/sect_07_01.html
answered 1 hour ago
marosgmarosg
46437
46437
add a comment |
add a comment |
The following runs the external command command
and returns its output.
"$(command)"
Without the brackets/parentheses, this would look for a variable instead of running a command:
"$variable"
As for the difference between $variable
and "$variable"
, this becomes relevant when $variable
contains spaces. When using "$variable"
, the entire variable contents will be inserted into a single string even if the contents include spaces. When using $variable
the contents of the variable may be expanded into an argument list of multiple arguments.
HI @thomasrutter, I'm sorry, i meant quotation mark ... I edit my comment now !
– Shankhara
1 hour ago
add a comment |
The following runs the external command command
and returns its output.
"$(command)"
Without the brackets/parentheses, this would look for a variable instead of running a command:
"$variable"
As for the difference between $variable
and "$variable"
, this becomes relevant when $variable
contains spaces. When using "$variable"
, the entire variable contents will be inserted into a single string even if the contents include spaces. When using $variable
the contents of the variable may be expanded into an argument list of multiple arguments.
HI @thomasrutter, I'm sorry, i meant quotation mark ... I edit my comment now !
– Shankhara
1 hour ago
add a comment |
The following runs the external command command
and returns its output.
"$(command)"
Without the brackets/parentheses, this would look for a variable instead of running a command:
"$variable"
As for the difference between $variable
and "$variable"
, this becomes relevant when $variable
contains spaces. When using "$variable"
, the entire variable contents will be inserted into a single string even if the contents include spaces. When using $variable
the contents of the variable may be expanded into an argument list of multiple arguments.
The following runs the external command command
and returns its output.
"$(command)"
Without the brackets/parentheses, this would look for a variable instead of running a command:
"$variable"
As for the difference between $variable
and "$variable"
, this becomes relevant when $variable
contains spaces. When using "$variable"
, the entire variable contents will be inserted into a single string even if the contents include spaces. When using $variable
the contents of the variable may be expanded into an argument list of multiple arguments.
edited 1 hour ago
answered 1 hour ago
thomasrutterthomasrutter
27.3k47089
27.3k47089
HI @thomasrutter, I'm sorry, i meant quotation mark ... I edit my comment now !
– Shankhara
1 hour ago
add a comment |
HI @thomasrutter, I'm sorry, i meant quotation mark ... I edit my comment now !
– Shankhara
1 hour ago
HI @thomasrutter, I'm sorry, i meant quotation mark ... I edit my comment now !
– Shankhara
1 hour ago
HI @thomasrutter, I'm sorry, i meant quotation mark ... I edit my comment now !
– Shankhara
1 hour ago
add a comment |
Quotation marks prevent word splitting - that is breaking down variables into multiple items at whitespaces (or to be more exact, at spaces, tabs, and newlines as defined in default value of $IFS
shell variable).
For example,
$ var="one two"
$ howmany(){ echo $#; }
$ howmany $var
2
$ howmany "$var"
1
Here we define howmany
function which just lets us know how many positional parameters are given. As you can see, there are two items being passed to the variable, and with the quotes the text in the variable is treated as one unit.
This is important for accurate passing of information. For example, if the variable contains path to file, and the filename contains spaces anywhere in the path, the command you are trying to run may fail or give inaccurate result. If we were trying to create file with $var
variable, touch $var
would create two files, but touch "$var"
just one.
Same goes for [ "$currentoutput" != "$lastoutput" ]
part. This particular test performs comparison on two strings. When the test runs, the [
command would need to see 3 arguments - a text string, the !=
operator, and another text string. Keeping double quotes prevents word splitting, and the [
commands sees exactly those 3 arguments. Now what happens if variables are unquoted ?
$ var="hello world"
$ foo="hi world"
$ [ $var != $foo ]
bash: [: too many arguments
$
Here, word splitting occurs, and instead [
sees two strings hello
and world
followed by !=
, followed by two other strings hi world
. Key point is that without double quotes, contents of variables are understood as separate units rather than one whole item.
Assigning command substitution doesn't require double quotes as in
var=$( df )
where you have df
command's output saved to var
. However, it is a good habit to always double quote variables and command substitution $(...)
unless you do in fact want the output to be treated as separate items.
On side note, the
while [ true ]
part can be
while true
[
is a command which evaluates its arguments, and [ whatever ]
is always true regardless of what is inside. By contrast, while true
uses the command true
which always returns success exit status (and that's exactly what while
loop needs). The difference is a bit more clarity and less testing performed. Alternatively, you could also use :
instead of true
The double quotes echo "" date and Time
part could probably be removed. They merely insert empty string and add extra space to the output. If that's desired, feel free to keep them there, but there's no particular functional value in this case.
lsusb >> test.log
This part could probably be replaced with echo "$currentoutput" >> test.log
. There's no reason to run lsusb
again after it has been ran already in currentoutput=$(lsusb)
. In cases where trailing newlines
have to be preserved in the output - one could see the value in running a command multiple times, but in case of lsusb
there's no need for that. The less external commands you call, the better, because every call to a non-built-in command costs in CPU, memory usage, and execution time ( even though the commands are probably pre-loaded from memory).
See also:
- When is double-quoting necessary?
- What is the point of the bash null operator : (colon)?
add a comment |
Quotation marks prevent word splitting - that is breaking down variables into multiple items at whitespaces (or to be more exact, at spaces, tabs, and newlines as defined in default value of $IFS
shell variable).
For example,
$ var="one two"
$ howmany(){ echo $#; }
$ howmany $var
2
$ howmany "$var"
1
Here we define howmany
function which just lets us know how many positional parameters are given. As you can see, there are two items being passed to the variable, and with the quotes the text in the variable is treated as one unit.
This is important for accurate passing of information. For example, if the variable contains path to file, and the filename contains spaces anywhere in the path, the command you are trying to run may fail or give inaccurate result. If we were trying to create file with $var
variable, touch $var
would create two files, but touch "$var"
just one.
Same goes for [ "$currentoutput" != "$lastoutput" ]
part. This particular test performs comparison on two strings. When the test runs, the [
command would need to see 3 arguments - a text string, the !=
operator, and another text string. Keeping double quotes prevents word splitting, and the [
commands sees exactly those 3 arguments. Now what happens if variables are unquoted ?
$ var="hello world"
$ foo="hi world"
$ [ $var != $foo ]
bash: [: too many arguments
$
Here, word splitting occurs, and instead [
sees two strings hello
and world
followed by !=
, followed by two other strings hi world
. Key point is that without double quotes, contents of variables are understood as separate units rather than one whole item.
Assigning command substitution doesn't require double quotes as in
var=$( df )
where you have df
command's output saved to var
. However, it is a good habit to always double quote variables and command substitution $(...)
unless you do in fact want the output to be treated as separate items.
On side note, the
while [ true ]
part can be
while true
[
is a command which evaluates its arguments, and [ whatever ]
is always true regardless of what is inside. By contrast, while true
uses the command true
which always returns success exit status (and that's exactly what while
loop needs). The difference is a bit more clarity and less testing performed. Alternatively, you could also use :
instead of true
The double quotes echo "" date and Time
part could probably be removed. They merely insert empty string and add extra space to the output. If that's desired, feel free to keep them there, but there's no particular functional value in this case.
lsusb >> test.log
This part could probably be replaced with echo "$currentoutput" >> test.log
. There's no reason to run lsusb
again after it has been ran already in currentoutput=$(lsusb)
. In cases where trailing newlines
have to be preserved in the output - one could see the value in running a command multiple times, but in case of lsusb
there's no need for that. The less external commands you call, the better, because every call to a non-built-in command costs in CPU, memory usage, and execution time ( even though the commands are probably pre-loaded from memory).
See also:
- When is double-quoting necessary?
- What is the point of the bash null operator : (colon)?
add a comment |
Quotation marks prevent word splitting - that is breaking down variables into multiple items at whitespaces (or to be more exact, at spaces, tabs, and newlines as defined in default value of $IFS
shell variable).
For example,
$ var="one two"
$ howmany(){ echo $#; }
$ howmany $var
2
$ howmany "$var"
1
Here we define howmany
function which just lets us know how many positional parameters are given. As you can see, there are two items being passed to the variable, and with the quotes the text in the variable is treated as one unit.
This is important for accurate passing of information. For example, if the variable contains path to file, and the filename contains spaces anywhere in the path, the command you are trying to run may fail or give inaccurate result. If we were trying to create file with $var
variable, touch $var
would create two files, but touch "$var"
just one.
Same goes for [ "$currentoutput" != "$lastoutput" ]
part. This particular test performs comparison on two strings. When the test runs, the [
command would need to see 3 arguments - a text string, the !=
operator, and another text string. Keeping double quotes prevents word splitting, and the [
commands sees exactly those 3 arguments. Now what happens if variables are unquoted ?
$ var="hello world"
$ foo="hi world"
$ [ $var != $foo ]
bash: [: too many arguments
$
Here, word splitting occurs, and instead [
sees two strings hello
and world
followed by !=
, followed by two other strings hi world
. Key point is that without double quotes, contents of variables are understood as separate units rather than one whole item.
Assigning command substitution doesn't require double quotes as in
var=$( df )
where you have df
command's output saved to var
. However, it is a good habit to always double quote variables and command substitution $(...)
unless you do in fact want the output to be treated as separate items.
On side note, the
while [ true ]
part can be
while true
[
is a command which evaluates its arguments, and [ whatever ]
is always true regardless of what is inside. By contrast, while true
uses the command true
which always returns success exit status (and that's exactly what while
loop needs). The difference is a bit more clarity and less testing performed. Alternatively, you could also use :
instead of true
The double quotes echo "" date and Time
part could probably be removed. They merely insert empty string and add extra space to the output. If that's desired, feel free to keep them there, but there's no particular functional value in this case.
lsusb >> test.log
This part could probably be replaced with echo "$currentoutput" >> test.log
. There's no reason to run lsusb
again after it has been ran already in currentoutput=$(lsusb)
. In cases where trailing newlines
have to be preserved in the output - one could see the value in running a command multiple times, but in case of lsusb
there's no need for that. The less external commands you call, the better, because every call to a non-built-in command costs in CPU, memory usage, and execution time ( even though the commands are probably pre-loaded from memory).
See also:
- When is double-quoting necessary?
- What is the point of the bash null operator : (colon)?
Quotation marks prevent word splitting - that is breaking down variables into multiple items at whitespaces (or to be more exact, at spaces, tabs, and newlines as defined in default value of $IFS
shell variable).
For example,
$ var="one two"
$ howmany(){ echo $#; }
$ howmany $var
2
$ howmany "$var"
1
Here we define howmany
function which just lets us know how many positional parameters are given. As you can see, there are two items being passed to the variable, and with the quotes the text in the variable is treated as one unit.
This is important for accurate passing of information. For example, if the variable contains path to file, and the filename contains spaces anywhere in the path, the command you are trying to run may fail or give inaccurate result. If we were trying to create file with $var
variable, touch $var
would create two files, but touch "$var"
just one.
Same goes for [ "$currentoutput" != "$lastoutput" ]
part. This particular test performs comparison on two strings. When the test runs, the [
command would need to see 3 arguments - a text string, the !=
operator, and another text string. Keeping double quotes prevents word splitting, and the [
commands sees exactly those 3 arguments. Now what happens if variables are unquoted ?
$ var="hello world"
$ foo="hi world"
$ [ $var != $foo ]
bash: [: too many arguments
$
Here, word splitting occurs, and instead [
sees two strings hello
and world
followed by !=
, followed by two other strings hi world
. Key point is that without double quotes, contents of variables are understood as separate units rather than one whole item.
Assigning command substitution doesn't require double quotes as in
var=$( df )
where you have df
command's output saved to var
. However, it is a good habit to always double quote variables and command substitution $(...)
unless you do in fact want the output to be treated as separate items.
On side note, the
while [ true ]
part can be
while true
[
is a command which evaluates its arguments, and [ whatever ]
is always true regardless of what is inside. By contrast, while true
uses the command true
which always returns success exit status (and that's exactly what while
loop needs). The difference is a bit more clarity and less testing performed. Alternatively, you could also use :
instead of true
The double quotes echo "" date and Time
part could probably be removed. They merely insert empty string and add extra space to the output. If that's desired, feel free to keep them there, but there's no particular functional value in this case.
lsusb >> test.log
This part could probably be replaced with echo "$currentoutput" >> test.log
. There's no reason to run lsusb
again after it has been ran already in currentoutput=$(lsusb)
. In cases where trailing newlines
have to be preserved in the output - one could see the value in running a command multiple times, but in case of lsusb
there's no need for that. The less external commands you call, the better, because every call to a non-built-in command costs in CPU, memory usage, and execution time ( even though the commands are probably pre-loaded from memory).
See also:
- When is double-quoting necessary?
- What is the point of the bash null operator : (colon)?
edited 8 mins ago
answered 32 mins ago
Sergiy KolodyazhnyySergiy Kolodyazhnyy
75.1k9155327
75.1k9155327
add a comment |
add a comment |
Shankhara is a new contributor. Be nice, and check out our Code of Conduct.
Shankhara is a new contributor. Be nice, and check out our Code of Conduct.
Shankhara is a new contributor. Be nice, and check out our Code of Conduct.
Shankhara is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Ask Ubuntu!
- 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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1133173%2fvariable-with-quotation-marks%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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