Bash string while loop
up vote
-2
down vote
favorite
Is there anyway to do while(string) just like what is in c
In c we have null terminator, but I'm not sure whether bash has it
while [ $string ] in bash will terminate when there is a space, which is not what I want, how do I detect whether it reaches the end of string or not?
bash shell
add a comment |
up vote
-2
down vote
favorite
Is there anyway to do while(string) just like what is in c
In c we have null terminator, but I'm not sure whether bash has it
while [ $string ] in bash will terminate when there is a space, which is not what I want, how do I detect whether it reaches the end of string or not?
bash shell
2
Welcome to StackOverflow! The answer to your question may very well be "Yes, there is a way". Please have a look at stackoverflow.com/help/how-to-ask for tips on improving this question. Meta-code, even, or working code in a language with which you're more familiar, will demonstrate how you're thinking a program should work, even if you don't know how to write it. If you can, try to make an MCVE, so that we can have some confidence we're actually working on the right problem.
– ghoti
Nov 22 at 1:33
That said, is this the kind of thing you're looking for?x="Hello"; for ((i=0; i<${#x}; i++)) { printf '> %sn' "${x:$i:1}"; }
– ghoti
Nov 22 at 1:37
add a comment |
up vote
-2
down vote
favorite
up vote
-2
down vote
favorite
Is there anyway to do while(string) just like what is in c
In c we have null terminator, but I'm not sure whether bash has it
while [ $string ] in bash will terminate when there is a space, which is not what I want, how do I detect whether it reaches the end of string or not?
bash shell
Is there anyway to do while(string) just like what is in c
In c we have null terminator, but I'm not sure whether bash has it
while [ $string ] in bash will terminate when there is a space, which is not what I want, how do I detect whether it reaches the end of string or not?
bash shell
bash shell
asked Nov 22 at 1:26
maple
13
13
2
Welcome to StackOverflow! The answer to your question may very well be "Yes, there is a way". Please have a look at stackoverflow.com/help/how-to-ask for tips on improving this question. Meta-code, even, or working code in a language with which you're more familiar, will demonstrate how you're thinking a program should work, even if you don't know how to write it. If you can, try to make an MCVE, so that we can have some confidence we're actually working on the right problem.
– ghoti
Nov 22 at 1:33
That said, is this the kind of thing you're looking for?x="Hello"; for ((i=0; i<${#x}; i++)) { printf '> %sn' "${x:$i:1}"; }
– ghoti
Nov 22 at 1:37
add a comment |
2
Welcome to StackOverflow! The answer to your question may very well be "Yes, there is a way". Please have a look at stackoverflow.com/help/how-to-ask for tips on improving this question. Meta-code, even, or working code in a language with which you're more familiar, will demonstrate how you're thinking a program should work, even if you don't know how to write it. If you can, try to make an MCVE, so that we can have some confidence we're actually working on the right problem.
– ghoti
Nov 22 at 1:33
That said, is this the kind of thing you're looking for?x="Hello"; for ((i=0; i<${#x}; i++)) { printf '> %sn' "${x:$i:1}"; }
– ghoti
Nov 22 at 1:37
2
2
Welcome to StackOverflow! The answer to your question may very well be "Yes, there is a way". Please have a look at stackoverflow.com/help/how-to-ask for tips on improving this question. Meta-code, even, or working code in a language with which you're more familiar, will demonstrate how you're thinking a program should work, even if you don't know how to write it. If you can, try to make an MCVE, so that we can have some confidence we're actually working on the right problem.
– ghoti
Nov 22 at 1:33
Welcome to StackOverflow! The answer to your question may very well be "Yes, there is a way". Please have a look at stackoverflow.com/help/how-to-ask for tips on improving this question. Meta-code, even, or working code in a language with which you're more familiar, will demonstrate how you're thinking a program should work, even if you don't know how to write it. If you can, try to make an MCVE, so that we can have some confidence we're actually working on the right problem.
– ghoti
Nov 22 at 1:33
That said, is this the kind of thing you're looking for?
x="Hello"; for ((i=0; i<${#x}; i++)) { printf '> %sn' "${x:$i:1}"; }
– ghoti
Nov 22 at 1:37
That said, is this the kind of thing you're looking for?
x="Hello"; for ((i=0; i<${#x}; i++)) { printf '> %sn' "${x:$i:1}"; }
– ghoti
Nov 22 at 1:37
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
I assume that the loop is removing part of the string and that it should stop when the string is empty. The way to do that in Bash is:
while [[ $string ]]
or (more explicitly)
while [[ -n $string ]]
For shells that don't have [[...]]
the equivalent is
while [ "$string" ]
or
while [ -n "$string" ]
The quotes are necessary to prevent various problems, including incorrect termination when the string contains only characters from $IFS
(including, normally, the space character). Use Shellcheck on shell code to detect many quoting problems, including the one in the question (SC2086: Double quote to prevent globbing and word splitting).
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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',
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%2fstackoverflow.com%2fquestions%2f53422678%2fbash-string-while-loop%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
up vote
0
down vote
I assume that the loop is removing part of the string and that it should stop when the string is empty. The way to do that in Bash is:
while [[ $string ]]
or (more explicitly)
while [[ -n $string ]]
For shells that don't have [[...]]
the equivalent is
while [ "$string" ]
or
while [ -n "$string" ]
The quotes are necessary to prevent various problems, including incorrect termination when the string contains only characters from $IFS
(including, normally, the space character). Use Shellcheck on shell code to detect many quoting problems, including the one in the question (SC2086: Double quote to prevent globbing and word splitting).
add a comment |
up vote
0
down vote
I assume that the loop is removing part of the string and that it should stop when the string is empty. The way to do that in Bash is:
while [[ $string ]]
or (more explicitly)
while [[ -n $string ]]
For shells that don't have [[...]]
the equivalent is
while [ "$string" ]
or
while [ -n "$string" ]
The quotes are necessary to prevent various problems, including incorrect termination when the string contains only characters from $IFS
(including, normally, the space character). Use Shellcheck on shell code to detect many quoting problems, including the one in the question (SC2086: Double quote to prevent globbing and word splitting).
add a comment |
up vote
0
down vote
up vote
0
down vote
I assume that the loop is removing part of the string and that it should stop when the string is empty. The way to do that in Bash is:
while [[ $string ]]
or (more explicitly)
while [[ -n $string ]]
For shells that don't have [[...]]
the equivalent is
while [ "$string" ]
or
while [ -n "$string" ]
The quotes are necessary to prevent various problems, including incorrect termination when the string contains only characters from $IFS
(including, normally, the space character). Use Shellcheck on shell code to detect many quoting problems, including the one in the question (SC2086: Double quote to prevent globbing and word splitting).
I assume that the loop is removing part of the string and that it should stop when the string is empty. The way to do that in Bash is:
while [[ $string ]]
or (more explicitly)
while [[ -n $string ]]
For shells that don't have [[...]]
the equivalent is
while [ "$string" ]
or
while [ -n "$string" ]
The quotes are necessary to prevent various problems, including incorrect termination when the string contains only characters from $IFS
(including, normally, the space character). Use Shellcheck on shell code to detect many quoting problems, including the one in the question (SC2086: Double quote to prevent globbing and word splitting).
answered Nov 22 at 20:44
pjh
1,584611
1,584611
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f53422678%2fbash-string-while-loop%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
2
Welcome to StackOverflow! The answer to your question may very well be "Yes, there is a way". Please have a look at stackoverflow.com/help/how-to-ask for tips on improving this question. Meta-code, even, or working code in a language with which you're more familiar, will demonstrate how you're thinking a program should work, even if you don't know how to write it. If you can, try to make an MCVE, so that we can have some confidence we're actually working on the right problem.
– ghoti
Nov 22 at 1:33
That said, is this the kind of thing you're looking for?
x="Hello"; for ((i=0; i<${#x}; i++)) { printf '> %sn' "${x:$i:1}"; }
– ghoti
Nov 22 at 1:37