How can I split a string to letters with IFS and read at no space/null, space and at a character -?
I have a string -w o rd
.
I need to split it to w o r d
or to an array for 'w' 'o' 'r' 'd'
it doesn't really matter.
I have tried the following
IFS='- ' read -a string <<< "-w o rd"
echo ${string[*]}
rd
isn't getting split. How can I make it get split
bash read
add a comment |
I have a string -w o rd
.
I need to split it to w o r d
or to an array for 'w' 'o' 'r' 'd'
it doesn't really matter.
I have tried the following
IFS='- ' read -a string <<< "-w o rd"
echo ${string[*]}
rd
isn't getting split. How can I make it get split
bash read
add a comment |
I have a string -w o rd
.
I need to split it to w o r d
or to an array for 'w' 'o' 'r' 'd'
it doesn't really matter.
I have tried the following
IFS='- ' read -a string <<< "-w o rd"
echo ${string[*]}
rd
isn't getting split. How can I make it get split
bash read
I have a string -w o rd
.
I need to split it to w o r d
or to an array for 'w' 'o' 'r' 'd'
it doesn't really matter.
I have tried the following
IFS='- ' read -a string <<< "-w o rd"
echo ${string[*]}
rd
isn't getting split. How can I make it get split
bash read
bash read
asked Dec 15 at 10:21
Bret Joseph
758
758
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
You can't use IFS in bash to split on nothing (it has to be on a character). There's no characters between r
and d
in rd
. No space and no character isn't the same as the null character.
If you want each character as a separate element in the array, one way I can think of is to read each character individually and append it to an array (and using IFS to get rid of spaces and -
):
bash-4.4$ while IFS=' -' read -n1 c ; do [[ -n $c ]] && foo+=("$c"); done <<<"-w o rd"
bash-4.4$ declare -p foo
declare -a foo=([0]="w" [1]="o" [2]="r" [3]="d")
add a comment |
You can remove the unwanted characters with ${var//pattern/replacement}
:
s='-w o rd'
s=${s//[- ]}
And then use the substring expansion to pick one character at a time:
$ for ((i=0; i < ${#s}; i++)); do
echo ${s:i:1}; # or do whatever you like here
done
(it even seems to work with multi-byte characters, at least on my system.)
Note that IFS='- '
will assign a literal backslash to IFS
as backslash has no special meaning within single quotes. The octal escape would work within $'...'
, but variables in Bash can't contain a NUL byte, so that doesn't help.
(The string gets cut on the NUL, so e.g. x=$'foobar'; printf "%qn" "$x"
prints just foo
. Also, what @muru said, splitting on a NUL byte is not the same as splitting between every character)
add a comment |
If your string isn't too long:
w='-w o rd baa'
w=${w//[!a-z]} # strip anything but lower case letters
eval echo '${w:'{0..10}':1}'
eval array=( '${w:'{0..10}':1}' )
echo "${array[@]}"
w o r d b a a
You can turn the silly thing into something nastier, IFS- and glob-safe and which takes into account the differences in the relative order of the brace and variable expansions between zsh
, bash
and ksh
:
args(){ printf '<%s> ' "$@"; echo; }
w='-e a * () n peek
fo*"x'"'q"
eval eval args "'"${w:'{0..$((${#w}-1))}':1}"'"
eval eval 'array=(' "'"${w:'{0..$((${#w}-1))}':1}"'" ')'
args "${array[@]}"
<-> <e> < > <a> < > <*> < > <(> <)> < > <> <n> < > <p> <e> <e> <k> <
> < > <f> <o> <*> <"> <x> <'> <q>
But franky, the only use of such monstrosity may be to scare off newbies and impress fools with assumed deep knowledge of shell language minutiae ;-)
add a comment |
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
});
}
});
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%2funix.stackexchange.com%2fquestions%2f488117%2fhow-can-i-split-a-string-to-letters-with-ifs-and-read-at-no-space-null-space-an%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
You can't use IFS in bash to split on nothing (it has to be on a character). There's no characters between r
and d
in rd
. No space and no character isn't the same as the null character.
If you want each character as a separate element in the array, one way I can think of is to read each character individually and append it to an array (and using IFS to get rid of spaces and -
):
bash-4.4$ while IFS=' -' read -n1 c ; do [[ -n $c ]] && foo+=("$c"); done <<<"-w o rd"
bash-4.4$ declare -p foo
declare -a foo=([0]="w" [1]="o" [2]="r" [3]="d")
add a comment |
You can't use IFS in bash to split on nothing (it has to be on a character). There's no characters between r
and d
in rd
. No space and no character isn't the same as the null character.
If you want each character as a separate element in the array, one way I can think of is to read each character individually and append it to an array (and using IFS to get rid of spaces and -
):
bash-4.4$ while IFS=' -' read -n1 c ; do [[ -n $c ]] && foo+=("$c"); done <<<"-w o rd"
bash-4.4$ declare -p foo
declare -a foo=([0]="w" [1]="o" [2]="r" [3]="d")
add a comment |
You can't use IFS in bash to split on nothing (it has to be on a character). There's no characters between r
and d
in rd
. No space and no character isn't the same as the null character.
If you want each character as a separate element in the array, one way I can think of is to read each character individually and append it to an array (and using IFS to get rid of spaces and -
):
bash-4.4$ while IFS=' -' read -n1 c ; do [[ -n $c ]] && foo+=("$c"); done <<<"-w o rd"
bash-4.4$ declare -p foo
declare -a foo=([0]="w" [1]="o" [2]="r" [3]="d")
You can't use IFS in bash to split on nothing (it has to be on a character). There's no characters between r
and d
in rd
. No space and no character isn't the same as the null character.
If you want each character as a separate element in the array, one way I can think of is to read each character individually and append it to an array (and using IFS to get rid of spaces and -
):
bash-4.4$ while IFS=' -' read -n1 c ; do [[ -n $c ]] && foo+=("$c"); done <<<"-w o rd"
bash-4.4$ declare -p foo
declare -a foo=([0]="w" [1]="o" [2]="r" [3]="d")
answered Dec 15 at 10:44
muru
1
1
add a comment |
add a comment |
You can remove the unwanted characters with ${var//pattern/replacement}
:
s='-w o rd'
s=${s//[- ]}
And then use the substring expansion to pick one character at a time:
$ for ((i=0; i < ${#s}; i++)); do
echo ${s:i:1}; # or do whatever you like here
done
(it even seems to work with multi-byte characters, at least on my system.)
Note that IFS='- '
will assign a literal backslash to IFS
as backslash has no special meaning within single quotes. The octal escape would work within $'...'
, but variables in Bash can't contain a NUL byte, so that doesn't help.
(The string gets cut on the NUL, so e.g. x=$'foobar'; printf "%qn" "$x"
prints just foo
. Also, what @muru said, splitting on a NUL byte is not the same as splitting between every character)
add a comment |
You can remove the unwanted characters with ${var//pattern/replacement}
:
s='-w o rd'
s=${s//[- ]}
And then use the substring expansion to pick one character at a time:
$ for ((i=0; i < ${#s}; i++)); do
echo ${s:i:1}; # or do whatever you like here
done
(it even seems to work with multi-byte characters, at least on my system.)
Note that IFS='- '
will assign a literal backslash to IFS
as backslash has no special meaning within single quotes. The octal escape would work within $'...'
, but variables in Bash can't contain a NUL byte, so that doesn't help.
(The string gets cut on the NUL, so e.g. x=$'foobar'; printf "%qn" "$x"
prints just foo
. Also, what @muru said, splitting on a NUL byte is not the same as splitting between every character)
add a comment |
You can remove the unwanted characters with ${var//pattern/replacement}
:
s='-w o rd'
s=${s//[- ]}
And then use the substring expansion to pick one character at a time:
$ for ((i=0; i < ${#s}; i++)); do
echo ${s:i:1}; # or do whatever you like here
done
(it even seems to work with multi-byte characters, at least on my system.)
Note that IFS='- '
will assign a literal backslash to IFS
as backslash has no special meaning within single quotes. The octal escape would work within $'...'
, but variables in Bash can't contain a NUL byte, so that doesn't help.
(The string gets cut on the NUL, so e.g. x=$'foobar'; printf "%qn" "$x"
prints just foo
. Also, what @muru said, splitting on a NUL byte is not the same as splitting between every character)
You can remove the unwanted characters with ${var//pattern/replacement}
:
s='-w o rd'
s=${s//[- ]}
And then use the substring expansion to pick one character at a time:
$ for ((i=0; i < ${#s}; i++)); do
echo ${s:i:1}; # or do whatever you like here
done
(it even seems to work with multi-byte characters, at least on my system.)
Note that IFS='- '
will assign a literal backslash to IFS
as backslash has no special meaning within single quotes. The octal escape would work within $'...'
, but variables in Bash can't contain a NUL byte, so that doesn't help.
(The string gets cut on the NUL, so e.g. x=$'foobar'; printf "%qn" "$x"
prints just foo
. Also, what @muru said, splitting on a NUL byte is not the same as splitting between every character)
answered Dec 16 at 10:29
ilkkachu
55.5k783151
55.5k783151
add a comment |
add a comment |
If your string isn't too long:
w='-w o rd baa'
w=${w//[!a-z]} # strip anything but lower case letters
eval echo '${w:'{0..10}':1}'
eval array=( '${w:'{0..10}':1}' )
echo "${array[@]}"
w o r d b a a
You can turn the silly thing into something nastier, IFS- and glob-safe and which takes into account the differences in the relative order of the brace and variable expansions between zsh
, bash
and ksh
:
args(){ printf '<%s> ' "$@"; echo; }
w='-e a * () n peek
fo*"x'"'q"
eval eval args "'"${w:'{0..$((${#w}-1))}':1}"'"
eval eval 'array=(' "'"${w:'{0..$((${#w}-1))}':1}"'" ')'
args "${array[@]}"
<-> <e> < > <a> < > <*> < > <(> <)> < > <> <n> < > <p> <e> <e> <k> <
> < > <f> <o> <*> <"> <x> <'> <q>
But franky, the only use of such monstrosity may be to scare off newbies and impress fools with assumed deep knowledge of shell language minutiae ;-)
add a comment |
If your string isn't too long:
w='-w o rd baa'
w=${w//[!a-z]} # strip anything but lower case letters
eval echo '${w:'{0..10}':1}'
eval array=( '${w:'{0..10}':1}' )
echo "${array[@]}"
w o r d b a a
You can turn the silly thing into something nastier, IFS- and glob-safe and which takes into account the differences in the relative order of the brace and variable expansions between zsh
, bash
and ksh
:
args(){ printf '<%s> ' "$@"; echo; }
w='-e a * () n peek
fo*"x'"'q"
eval eval args "'"${w:'{0..$((${#w}-1))}':1}"'"
eval eval 'array=(' "'"${w:'{0..$((${#w}-1))}':1}"'" ')'
args "${array[@]}"
<-> <e> < > <a> < > <*> < > <(> <)> < > <> <n> < > <p> <e> <e> <k> <
> < > <f> <o> <*> <"> <x> <'> <q>
But franky, the only use of such monstrosity may be to scare off newbies and impress fools with assumed deep knowledge of shell language minutiae ;-)
add a comment |
If your string isn't too long:
w='-w o rd baa'
w=${w//[!a-z]} # strip anything but lower case letters
eval echo '${w:'{0..10}':1}'
eval array=( '${w:'{0..10}':1}' )
echo "${array[@]}"
w o r d b a a
You can turn the silly thing into something nastier, IFS- and glob-safe and which takes into account the differences in the relative order of the brace and variable expansions between zsh
, bash
and ksh
:
args(){ printf '<%s> ' "$@"; echo; }
w='-e a * () n peek
fo*"x'"'q"
eval eval args "'"${w:'{0..$((${#w}-1))}':1}"'"
eval eval 'array=(' "'"${w:'{0..$((${#w}-1))}':1}"'" ')'
args "${array[@]}"
<-> <e> < > <a> < > <*> < > <(> <)> < > <> <n> < > <p> <e> <e> <k> <
> < > <f> <o> <*> <"> <x> <'> <q>
But franky, the only use of such monstrosity may be to scare off newbies and impress fools with assumed deep knowledge of shell language minutiae ;-)
If your string isn't too long:
w='-w o rd baa'
w=${w//[!a-z]} # strip anything but lower case letters
eval echo '${w:'{0..10}':1}'
eval array=( '${w:'{0..10}':1}' )
echo "${array[@]}"
w o r d b a a
You can turn the silly thing into something nastier, IFS- and glob-safe and which takes into account the differences in the relative order of the brace and variable expansions between zsh
, bash
and ksh
:
args(){ printf '<%s> ' "$@"; echo; }
w='-e a * () n peek
fo*"x'"'q"
eval eval args "'"${w:'{0..$((${#w}-1))}':1}"'"
eval eval 'array=(' "'"${w:'{0..$((${#w}-1))}':1}"'" ')'
args "${array[@]}"
<-> <e> < > <a> < > <*> < > <(> <)> < > <> <n> < > <p> <e> <e> <k> <
> < > <f> <o> <*> <"> <x> <'> <q>
But franky, the only use of such monstrosity may be to scare off newbies and impress fools with assumed deep knowledge of shell language minutiae ;-)
edited Dec 23 at 5:03
answered Dec 17 at 1:32
Uncle Billy
3035
3035
add a comment |
add a comment |
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.
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%2funix.stackexchange.com%2fquestions%2f488117%2fhow-can-i-split-a-string-to-letters-with-ifs-and-read-at-no-space-null-space-an%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