Nested double quotes for wrapping variables












0














There is one line in my bash script file like this:



echo "$string" | sed -e "s|($str)|$(wrap \1 $1 $2)|"


Now, I want to wrap the $1 and $2 with double quotes for preventing errors while $1 equals to null.



I tried to add before ", like ""$1" "$2"" but it does not work.



How can I do that?










share|improve this question


















  • 4




    Using shell variables and command substitutions to generate a sed script is terribly fragile. Could you explain what $string and $str are and what you want to achieve. Are you generating commands that you later execute?
    – Kusalananda
    Dec 12 at 10:24








  • 1




    and as always, when writing "but it does not work", please show the exact command(s) you've entered, the result, any error messages you get, and what you expected to get instead.
    – ilkkachu
    Dec 12 at 10:46












  • Do you expect wrap to be invoked for every line with the captured string as argument or do you expect wrap to be given a literal 1 as argument and its output to be used to generate the content of the sed inline script?
    – Stéphane Chazelas
    Dec 12 at 13:19
















0














There is one line in my bash script file like this:



echo "$string" | sed -e "s|($str)|$(wrap \1 $1 $2)|"


Now, I want to wrap the $1 and $2 with double quotes for preventing errors while $1 equals to null.



I tried to add before ", like ""$1" "$2"" but it does not work.



How can I do that?










share|improve this question


















  • 4




    Using shell variables and command substitutions to generate a sed script is terribly fragile. Could you explain what $string and $str are and what you want to achieve. Are you generating commands that you later execute?
    – Kusalananda
    Dec 12 at 10:24








  • 1




    and as always, when writing "but it does not work", please show the exact command(s) you've entered, the result, any error messages you get, and what you expected to get instead.
    – ilkkachu
    Dec 12 at 10:46












  • Do you expect wrap to be invoked for every line with the captured string as argument or do you expect wrap to be given a literal 1 as argument and its output to be used to generate the content of the sed inline script?
    – Stéphane Chazelas
    Dec 12 at 13:19














0












0








0







There is one line in my bash script file like this:



echo "$string" | sed -e "s|($str)|$(wrap \1 $1 $2)|"


Now, I want to wrap the $1 and $2 with double quotes for preventing errors while $1 equals to null.



I tried to add before ", like ""$1" "$2"" but it does not work.



How can I do that?










share|improve this question













There is one line in my bash script file like this:



echo "$string" | sed -e "s|($str)|$(wrap \1 $1 $2)|"


Now, I want to wrap the $1 and $2 with double quotes for preventing errors while $1 equals to null.



I tried to add before ", like ""$1" "$2"" but it does not work.



How can I do that?







bash shell






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 12 at 10:20









LCB

1012




1012








  • 4




    Using shell variables and command substitutions to generate a sed script is terribly fragile. Could you explain what $string and $str are and what you want to achieve. Are you generating commands that you later execute?
    – Kusalananda
    Dec 12 at 10:24








  • 1




    and as always, when writing "but it does not work", please show the exact command(s) you've entered, the result, any error messages you get, and what you expected to get instead.
    – ilkkachu
    Dec 12 at 10:46












  • Do you expect wrap to be invoked for every line with the captured string as argument or do you expect wrap to be given a literal 1 as argument and its output to be used to generate the content of the sed inline script?
    – Stéphane Chazelas
    Dec 12 at 13:19














  • 4




    Using shell variables and command substitutions to generate a sed script is terribly fragile. Could you explain what $string and $str are and what you want to achieve. Are you generating commands that you later execute?
    – Kusalananda
    Dec 12 at 10:24








  • 1




    and as always, when writing "but it does not work", please show the exact command(s) you've entered, the result, any error messages you get, and what you expected to get instead.
    – ilkkachu
    Dec 12 at 10:46












  • Do you expect wrap to be invoked for every line with the captured string as argument or do you expect wrap to be given a literal 1 as argument and its output to be used to generate the content of the sed inline script?
    – Stéphane Chazelas
    Dec 12 at 13:19








4




4




Using shell variables and command substitutions to generate a sed script is terribly fragile. Could you explain what $string and $str are and what you want to achieve. Are you generating commands that you later execute?
– Kusalananda
Dec 12 at 10:24






Using shell variables and command substitutions to generate a sed script is terribly fragile. Could you explain what $string and $str are and what you want to achieve. Are you generating commands that you later execute?
– Kusalananda
Dec 12 at 10:24






1




1




and as always, when writing "but it does not work", please show the exact command(s) you've entered, the result, any error messages you get, and what you expected to get instead.
– ilkkachu
Dec 12 at 10:46






and as always, when writing "but it does not work", please show the exact command(s) you've entered, the result, any error messages you get, and what you expected to get instead.
– ilkkachu
Dec 12 at 10:46














Do you expect wrap to be invoked for every line with the captured string as argument or do you expect wrap to be given a literal 1 as argument and its output to be used to generate the content of the sed inline script?
– Stéphane Chazelas
Dec 12 at 13:19




Do you expect wrap to be invoked for every line with the captured string as argument or do you expect wrap to be given a literal 1 as argument and its output to be used to generate the content of the sed inline script?
– Stéphane Chazelas
Dec 12 at 13:19










1 Answer
1






active

oldest

votes


















0














I got the answer finally. I misunderstood the effect of double quotes. Actually, I only need to surround the characters that I need. So, I change the code like this:



echo "$string" | sed -e "s|($str)|"$(wrap \1 "$1" "$2")"|g"





share|improve this answer





















  • Yes. You are in a subshell inside the parentheses, so quotes in there are not affected by "outer" quotes.
    – glenn jackman
    Dec 12 at 16:04











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%2f487545%2fnested-double-quotes-for-wrapping-variables%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









0














I got the answer finally. I misunderstood the effect of double quotes. Actually, I only need to surround the characters that I need. So, I change the code like this:



echo "$string" | sed -e "s|($str)|"$(wrap \1 "$1" "$2")"|g"





share|improve this answer





















  • Yes. You are in a subshell inside the parentheses, so quotes in there are not affected by "outer" quotes.
    – glenn jackman
    Dec 12 at 16:04
















0














I got the answer finally. I misunderstood the effect of double quotes. Actually, I only need to surround the characters that I need. So, I change the code like this:



echo "$string" | sed -e "s|($str)|"$(wrap \1 "$1" "$2")"|g"





share|improve this answer





















  • Yes. You are in a subshell inside the parentheses, so quotes in there are not affected by "outer" quotes.
    – glenn jackman
    Dec 12 at 16:04














0












0








0






I got the answer finally. I misunderstood the effect of double quotes. Actually, I only need to surround the characters that I need. So, I change the code like this:



echo "$string" | sed -e "s|($str)|"$(wrap \1 "$1" "$2")"|g"





share|improve this answer












I got the answer finally. I misunderstood the effect of double quotes. Actually, I only need to surround the characters that I need. So, I change the code like this:



echo "$string" | sed -e "s|($str)|"$(wrap \1 "$1" "$2")"|g"






share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 12 at 13:13









LCB

1012




1012












  • Yes. You are in a subshell inside the parentheses, so quotes in there are not affected by "outer" quotes.
    – glenn jackman
    Dec 12 at 16:04


















  • Yes. You are in a subshell inside the parentheses, so quotes in there are not affected by "outer" quotes.
    – glenn jackman
    Dec 12 at 16:04
















Yes. You are in a subshell inside the parentheses, so quotes in there are not affected by "outer" quotes.
– glenn jackman
Dec 12 at 16:04




Yes. You are in a subshell inside the parentheses, so quotes in there are not affected by "outer" quotes.
– glenn jackman
Dec 12 at 16:04


















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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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%2f487545%2fnested-double-quotes-for-wrapping-variables%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

Morgemoulin

Scott Moir

Souastre