Wrong string concatenation using Bash Windows Subsystem
I'm having headaches to know why my script doesn't work as expected under windows subsystem linux.
My version from the store : Debian GNU/Linux 9.6 (stretch) (I tried ubuntu too, with the same results)
And my bash version : GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)
This is my basic script only to show the issue :
PROJECT_ENV="development"
echo $PROJECT_ENV
compose_file="docker-compose.${PROJECT_ENV}.build.yml"
echo $compose_file
And it outputs :
.build.ymlpose.development
As i understand, that output doesn't make any sense to me, I tried to reinstall bash but i'm still having the same issue.
linux bash windows-subsystem-for-linux string concatenation
asked Dec 16 at 21:40
waken22
132
add a comment |
I'm having headaches to know why my script doesn't work as expected under windows subsystem linux.
My version from the store : Debian GNU/Linux 9.6 (stretch) (I tried ubuntu too, with the same results)
And my bash version : GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)
This is my basic script only to show the issue :
PROJECT_ENV="development"
echo $PROJECT_ENV
compose_file="docker-compose.${PROJECT_ENV}.build.yml"
echo $compose_file
And it outputs :
.build.ymlpose.development
As i understand, that output doesn't make any sense to me, I tried to reinstall bash but i'm still having the same issue.
linux bash windows-subsystem-for-linux string concatenation
asked Dec 16 at 21:40
waken22
132
add a comment |
I'm having headaches to know why my script doesn't work as expected under windows subsystem linux.
My version from the store : Debian GNU/Linux 9.6 (stretch) (I tried ubuntu too, with the same results)
And my bash version : GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)
This is my basic script only to show the issue :
PROJECT_ENV="development"
echo $PROJECT_ENV
compose_file="docker-compose.${PROJECT_ENV}.build.yml"
echo $compose_file
And it outputs :
.build.ymlpose.development
As i understand, that output doesn't make any sense to me, I tried to reinstall bash but i'm still having the same issue.
linux bash windows-subsystem-for-linux string concatenation
asked Dec 16 at 21:40
waken22
132
I'm having headaches to know why my script doesn't work as expected under windows subsystem linux.
My version from the store : Debian GNU/Linux 9.6 (stretch) (I tried ubuntu too, with the same results)
And my bash version : GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)
This is my basic script only to show the issue :
PROJECT_ENV="development"
echo $PROJECT_ENV
compose_file="docker-compose.${PROJECT_ENV}.build.yml"
echo $compose_file
And it outputs :
.build.ymlpose.development
As i understand, that output doesn't make any sense to me, I tried to reinstall bash but i'm still having the same issue.
linux bash windows-subsystem-for-linux string concatenation
linux bash windows-subsystem-for-linux string concatenation
asked Dec 16 at 21:40
waken22
132
asked Dec 16 at 21:40
waken22
132
asked Dec 16 at 21:40
waken22
132
asked Dec 16 at 21:40
waken22
132
asked Dec 16 at 21:40
waken22
132
132
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
There is a carriage return character at the end of PROJECT_ENV variable content. This is probably because your script uses CR+LF line endings (proper in DOS/Windows) instead of sole LF (Unix/Linux).
In Linux dos2unix is the right tool to fix it.
The detailed explanation is as follows:
The final
echoprints
docker-compose.development
CRmakes the terminal go back to the beginning of the line.
The consecutive characters overwrite the previous text:
.build.yml
Therefore the result is:
.build.ymlpose.development
answered Dec 16 at 21:44
Kamil Maciorowski
24.4k155177
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});
}
});
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%2fsuperuser.com%2fquestions%2f1385082%2fwrong-string-concatenation-using-bash-windows-subsystem%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
There is a carriage return character at the end of PROJECT_ENV variable content. This is probably because your script uses CR+LF line endings (proper in DOS/Windows) instead of sole LF (Unix/Linux).
In Linux dos2unix is the right tool to fix it.
The detailed explanation is as follows:
The final
echoprints
docker-compose.development
CRmakes the terminal go back to the beginning of the line.
The consecutive characters overwrite the previous text:
.build.yml
Therefore the result is:
.build.ymlpose.development
answered Dec 16 at 21:44
Kamil Maciorowski
24.4k155177
add a comment |
There is a carriage return character at the end of PROJECT_ENV variable content. This is probably because your script uses CR+LF line endings (proper in DOS/Windows) instead of sole LF (Unix/Linux).
In Linux dos2unix is the right tool to fix it.
The detailed explanation is as follows:
The final
echoprints
docker-compose.development
CRmakes the terminal go back to the beginning of the line.
The consecutive characters overwrite the previous text:
.build.yml
Therefore the result is:
.build.ymlpose.development
answered Dec 16 at 21:44
Kamil Maciorowski
24.4k155177
add a comment |
There is a carriage return character at the end of PROJECT_ENV variable content. This is probably because your script uses CR+LF line endings (proper in DOS/Windows) instead of sole LF (Unix/Linux).
In Linux dos2unix is the right tool to fix it.
The detailed explanation is as follows:
The final
echoprints
docker-compose.development
CRmakes the terminal go back to the beginning of the line.
The consecutive characters overwrite the previous text:
.build.yml
Therefore the result is:
.build.ymlpose.development
answered Dec 16 at 21:44
Kamil Maciorowski
24.4k155177
There is a carriage return character at the end of PROJECT_ENV variable content. This is probably because your script uses CR+LF line endings (proper in DOS/Windows) instead of sole LF (Unix/Linux).
In Linux dos2unix is the right tool to fix it.
The detailed explanation is as follows:
The final
echoprints
docker-compose.development
CRmakes the terminal go back to the beginning of the line.
The consecutive characters overwrite the previous text:
.build.yml
Therefore the result is:
.build.ymlpose.development
answered Dec 16 at 21:44
Kamil Maciorowski
24.4k155177
edited Dec 16 at 22:04
answered Dec 16 at 21:44
Kamil Maciorowski
24.4k155177
answered Dec 16 at 21:44
Kamil Maciorowski
24.4k155177
answered Dec 16 at 21:44
Kamil Maciorowski
24.4k155177
24.4k155177
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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.
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%2fsuperuser.com%2fquestions%2f1385082%2fwrong-string-concatenation-using-bash-windows-subsystem%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
