NUL delimited variableHow to name a file in the deepest level of a directory treeUsing a variable inside a sequence of commands in bash to supplement an existing string - syntax error or flawed design?How to use bash's complete or compgen -C (command) option?how to get the standard output from command in variableSaving command output to a variable in bash results in “Unescaped left brace in regex is deprecated”Confusion about bash command vs. variable substitutionHow to iterate a command with two different variables?tail/head piping remove newlinesPotential workaround to inotifywait can't produce NUL-delimited outputHow can I prevent command substitution from removing NUL and trailing newline(s)?

Wilcoxon signed rank test – critical value for n>50

Are there any vegetarian astronauts?

Can you get infinite turns with this 2 card combo?

How can I convince my reader that I will not use a certain trope?

Anagram Within an Anagram!

Magnitude of vector quantities

Do equal angles necessarily mean a polygon is regular?

How can I check type T is among parameter pack Ts... in C++?

Three column layout

Confusion about multiple information Sets

Why aren't (poly-)cotton tents more popular?

can’t run a function against EXEC

Generate and Graph the Recamán Sequence

Was touching your nose a greeting in second millenium Mesopotamia?

Why cruise at 7000' in an A319?

Should I include salary information on my CV?

Why is the Turkish president's surname spelt in Russian as Эрдоган, with г?

Are Finite Automata Turing Complete?

What is the line crossing the Pacific Ocean that is shown on maps?

Should I hide continue button until tasks are completed?

Signing using digital signatures?

Children's short story about material that accelerates away from gravity

How do I find and plot the intersection of these three surfaces?

Does anycast addressing add additional latency in any way?



NUL delimited variable


How to name a file in the deepest level of a directory treeUsing a variable inside a sequence of commands in bash to supplement an existing string - syntax error or flawed design?How to use bash's complete or compgen -C (command) option?how to get the standard output from command in variableSaving command output to a variable in bash results in “Unescaped left brace in regex is deprecated”Confusion about bash command vs. variable substitutionHow to iterate a command with two different variables?tail/head piping remove newlinesPotential workaround to inotifywait can't produce NUL-delimited outputHow can I prevent command substitution from removing NUL and trailing newline(s)?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








3















GNU bash, version 4.4.19(1)-release (x86_64-pc-linux-gnu)



Idea is to set a variable to a NUL delimited data set. Here $samples



This, however, result in:




warning: command substitution: ignored null byte in input




when doing:



samples="$(find . -type d -iregex './sample[0-9][0-9]' -printf "%f" | sort -z)"


Thought I could re-use this variable as I need to iterate the same values multiple times:



while IFS= read -rd '' sample; do
echo $sample
done<<< "$samples"


I could use n over in the find command in this exact case, but would like to know how, if possible, to do it with NUL delimiter generally speaking.



Optionally I could do:



while IFS= read -rd '' sample; do
echo $sample
done< <(find . -type d -iregex './E[0-9][0-9]' -printf "%f" | sort -z)


but - as I need to loop it several times it makes for some very redundant code - and would have to run the find and sort command each time.



Convert the result into an array perhaps?




  • Is this possible?

  • Why can not NUL delimited data be used as is?









share|improve this question



















  • 1





    See also Why is looping over find's output bad practice? where several approaches are given to loop over find's output reliably.

    – Stéphane Chazelas
    Jun 9 at 17:33











  • Why are you sorting the filenames? They would be sorted lexicographically anyway.

    – Kusalananda
    Jun 9 at 18:25






  • 1





    @Kusalananda: Not in result from find. The inode table (or Directory Entries is perhaps more correct) is not sorted. No idea how find is implemented, but if it uses readdir, it is unlikely the names will be sorted in any fashion, man7.org/linux/man-pages/man3/readdir.3.html#NOTES and ext4.wiki.kernel.org/index.php/… so perhaps in some hash order. en.wikipedia.org/wiki/HTree

    – user3342816
    Jun 9 at 19:03












  • @user3342816 Ah, yes. Your are absolutely correct. Sorry for the noise.

    – Kusalananda
    Jun 9 at 19:06

















3















GNU bash, version 4.4.19(1)-release (x86_64-pc-linux-gnu)



Idea is to set a variable to a NUL delimited data set. Here $samples



This, however, result in:




warning: command substitution: ignored null byte in input




when doing:



samples="$(find . -type d -iregex './sample[0-9][0-9]' -printf "%f" | sort -z)"


Thought I could re-use this variable as I need to iterate the same values multiple times:



while IFS= read -rd '' sample; do
echo $sample
done<<< "$samples"


I could use n over in the find command in this exact case, but would like to know how, if possible, to do it with NUL delimiter generally speaking.



Optionally I could do:



while IFS= read -rd '' sample; do
echo $sample
done< <(find . -type d -iregex './E[0-9][0-9]' -printf "%f" | sort -z)


but - as I need to loop it several times it makes for some very redundant code - and would have to run the find and sort command each time.



Convert the result into an array perhaps?




  • Is this possible?

  • Why can not NUL delimited data be used as is?









share|improve this question



















  • 1





    See also Why is looping over find's output bad practice? where several approaches are given to loop over find's output reliably.

    – Stéphane Chazelas
    Jun 9 at 17:33











  • Why are you sorting the filenames? They would be sorted lexicographically anyway.

    – Kusalananda
    Jun 9 at 18:25






  • 1





    @Kusalananda: Not in result from find. The inode table (or Directory Entries is perhaps more correct) is not sorted. No idea how find is implemented, but if it uses readdir, it is unlikely the names will be sorted in any fashion, man7.org/linux/man-pages/man3/readdir.3.html#NOTES and ext4.wiki.kernel.org/index.php/… so perhaps in some hash order. en.wikipedia.org/wiki/HTree

    – user3342816
    Jun 9 at 19:03












  • @user3342816 Ah, yes. Your are absolutely correct. Sorry for the noise.

    – Kusalananda
    Jun 9 at 19:06













3












3








3


1






GNU bash, version 4.4.19(1)-release (x86_64-pc-linux-gnu)



Idea is to set a variable to a NUL delimited data set. Here $samples



This, however, result in:




warning: command substitution: ignored null byte in input




when doing:



samples="$(find . -type d -iregex './sample[0-9][0-9]' -printf "%f" | sort -z)"


Thought I could re-use this variable as I need to iterate the same values multiple times:



while IFS= read -rd '' sample; do
echo $sample
done<<< "$samples"


I could use n over in the find command in this exact case, but would like to know how, if possible, to do it with NUL delimiter generally speaking.



Optionally I could do:



while IFS= read -rd '' sample; do
echo $sample
done< <(find . -type d -iregex './E[0-9][0-9]' -printf "%f" | sort -z)


but - as I need to loop it several times it makes for some very redundant code - and would have to run the find and sort command each time.



Convert the result into an array perhaps?




  • Is this possible?

  • Why can not NUL delimited data be used as is?









share|improve this question
















GNU bash, version 4.4.19(1)-release (x86_64-pc-linux-gnu)



Idea is to set a variable to a NUL delimited data set. Here $samples



This, however, result in:




warning: command substitution: ignored null byte in input




when doing:



samples="$(find . -type d -iregex './sample[0-9][0-9]' -printf "%f" | sort -z)"


Thought I could re-use this variable as I need to iterate the same values multiple times:



while IFS= read -rd '' sample; do
echo $sample
done<<< "$samples"


I could use n over in the find command in this exact case, but would like to know how, if possible, to do it with NUL delimiter generally speaking.



Optionally I could do:



while IFS= read -rd '' sample; do
echo $sample
done< <(find . -type d -iregex './E[0-9][0-9]' -printf "%f" | sort -z)


but - as I need to loop it several times it makes for some very redundant code - and would have to run the find and sort command each time.



Convert the result into an array perhaps?




  • Is this possible?

  • Why can not NUL delimited data be used as is?






bash command-substitution






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 9 at 16:52









ilkkachu

64.6k10 gold badges108 silver badges187 bronze badges




64.6k10 gold badges108 silver badges187 bronze badges










asked Jun 9 at 15:56









user3342816user3342816

717 bronze badges




717 bronze badges







  • 1





    See also Why is looping over find's output bad practice? where several approaches are given to loop over find's output reliably.

    – Stéphane Chazelas
    Jun 9 at 17:33











  • Why are you sorting the filenames? They would be sorted lexicographically anyway.

    – Kusalananda
    Jun 9 at 18:25






  • 1





    @Kusalananda: Not in result from find. The inode table (or Directory Entries is perhaps more correct) is not sorted. No idea how find is implemented, but if it uses readdir, it is unlikely the names will be sorted in any fashion, man7.org/linux/man-pages/man3/readdir.3.html#NOTES and ext4.wiki.kernel.org/index.php/… so perhaps in some hash order. en.wikipedia.org/wiki/HTree

    – user3342816
    Jun 9 at 19:03












  • @user3342816 Ah, yes. Your are absolutely correct. Sorry for the noise.

    – Kusalananda
    Jun 9 at 19:06












  • 1





    See also Why is looping over find's output bad practice? where several approaches are given to loop over find's output reliably.

    – Stéphane Chazelas
    Jun 9 at 17:33











  • Why are you sorting the filenames? They would be sorted lexicographically anyway.

    – Kusalananda
    Jun 9 at 18:25






  • 1





    @Kusalananda: Not in result from find. The inode table (or Directory Entries is perhaps more correct) is not sorted. No idea how find is implemented, but if it uses readdir, it is unlikely the names will be sorted in any fashion, man7.org/linux/man-pages/man3/readdir.3.html#NOTES and ext4.wiki.kernel.org/index.php/… so perhaps in some hash order. en.wikipedia.org/wiki/HTree

    – user3342816
    Jun 9 at 19:03












  • @user3342816 Ah, yes. Your are absolutely correct. Sorry for the noise.

    – Kusalananda
    Jun 9 at 19:06







1




1





See also Why is looping over find's output bad practice? where several approaches are given to loop over find's output reliably.

– Stéphane Chazelas
Jun 9 at 17:33





See also Why is looping over find's output bad practice? where several approaches are given to loop over find's output reliably.

– Stéphane Chazelas
Jun 9 at 17:33













Why are you sorting the filenames? They would be sorted lexicographically anyway.

– Kusalananda
Jun 9 at 18:25





Why are you sorting the filenames? They would be sorted lexicographically anyway.

– Kusalananda
Jun 9 at 18:25




1




1





@Kusalananda: Not in result from find. The inode table (or Directory Entries is perhaps more correct) is not sorted. No idea how find is implemented, but if it uses readdir, it is unlikely the names will be sorted in any fashion, man7.org/linux/man-pages/man3/readdir.3.html#NOTES and ext4.wiki.kernel.org/index.php/… so perhaps in some hash order. en.wikipedia.org/wiki/HTree

– user3342816
Jun 9 at 19:03






@Kusalananda: Not in result from find. The inode table (or Directory Entries is perhaps more correct) is not sorted. No idea how find is implemented, but if it uses readdir, it is unlikely the names will be sorted in any fashion, man7.org/linux/man-pages/man3/readdir.3.html#NOTES and ext4.wiki.kernel.org/index.php/… so perhaps in some hash order. en.wikipedia.org/wiki/HTree

– user3342816
Jun 9 at 19:03














@user3342816 Ah, yes. Your are absolutely correct. Sorry for the noise.

– Kusalananda
Jun 9 at 19:06





@user3342816 Ah, yes. Your are absolutely correct. Sorry for the noise.

– Kusalananda
Jun 9 at 19:06










2 Answers
2






active

oldest

votes


















6














It is a fact that you can't store null bytes in a bash string context, because of the underlying C implementation. See Why $'' or $'x0' is an empty string? Should be the null-character, isn't it?.



One option would be strip off the null bytes after the sort command, at the end of the pipeline using tr and store the result to solve the immediate problem of the warning message thrown. But that would still leave your logic flawed as the filenames with newlines would still be broken.



Use an array, use the mapfile or readarray command (on bash 4.4+) to directly slurp in the results from the find command



IFS= readarray -t -d '' samples < <(find . -type d -iregex './sample[0-9][0-9]' -printf "%f" | sort -z)





share|improve this answer

























  • Thank you. But would it not then be the same as using -printf "%fn"? If one are separating with newline in the result one are assuming there are no newlines in the data anyway (if you get what I mean). The whole point of using zero delimiter is to be sure one do not split names with newlines in them …

    – user3342816
    Jun 9 at 16:24











  • @user3342816: I thought your intention was to run the find command once, so after sorting the results, you wouldn't need the null delimited output anymore, so store the result in the variable without it

    – Inian
    Jun 9 at 16:27












  • From the link you posted (tried to find something like that first) I read it as it is not possible to store zero in a var, so that much set array to be the "only" option.

    – user3342816
    Jun 9 at 16:27











  • Yes. That was the intention. But if a value can have new-line, the result would be ambiguous even if sorted correctly.

    – user3342816
    Jun 9 at 16:29











  • @user3342816 : Then I suppose the readarray option is the one you want

    – Inian
    Jun 9 at 16:33


















6














The bash shell does not support what you want to do. The zsh shell does out of the box.



% mkdir sample11 SAMple12 sample21 sample22 dir1
% ll
total 20
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 dir1
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 sample11
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 SAMple12
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 sample21
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 sample22
% samples=$(find . -type d -iregex './sample[0-9][0-9]' -print0 | sort -z)
% echo $samples
./sample11./SAMple12./sample21./sample22
% echo $samples | od -a
0000000 . / s a m p l e 1 1 nul . / S A M
0000020 p l e 1 2 nul . / s a m p l e 2 1
0000040 nul . / s a m p l e 2 2 nul nl
0000055
%





share|improve this answer




















  • 1





    ... however, please beware that the value of the environment variable samples will be truncated at the nul byte when being passed to child processes: If you perform export samples and start a child instance of zsh, $samples will only be ./sample11 in the child instance.

    – Martin Rosenau
    Jun 10 at 8:10













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%2f523855%2fnul-delimited-variable%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









6














It is a fact that you can't store null bytes in a bash string context, because of the underlying C implementation. See Why $'' or $'x0' is an empty string? Should be the null-character, isn't it?.



One option would be strip off the null bytes after the sort command, at the end of the pipeline using tr and store the result to solve the immediate problem of the warning message thrown. But that would still leave your logic flawed as the filenames with newlines would still be broken.



Use an array, use the mapfile or readarray command (on bash 4.4+) to directly slurp in the results from the find command



IFS= readarray -t -d '' samples < <(find . -type d -iregex './sample[0-9][0-9]' -printf "%f" | sort -z)





share|improve this answer

























  • Thank you. But would it not then be the same as using -printf "%fn"? If one are separating with newline in the result one are assuming there are no newlines in the data anyway (if you get what I mean). The whole point of using zero delimiter is to be sure one do not split names with newlines in them …

    – user3342816
    Jun 9 at 16:24











  • @user3342816: I thought your intention was to run the find command once, so after sorting the results, you wouldn't need the null delimited output anymore, so store the result in the variable without it

    – Inian
    Jun 9 at 16:27












  • From the link you posted (tried to find something like that first) I read it as it is not possible to store zero in a var, so that much set array to be the "only" option.

    – user3342816
    Jun 9 at 16:27











  • Yes. That was the intention. But if a value can have new-line, the result would be ambiguous even if sorted correctly.

    – user3342816
    Jun 9 at 16:29











  • @user3342816 : Then I suppose the readarray option is the one you want

    – Inian
    Jun 9 at 16:33















6














It is a fact that you can't store null bytes in a bash string context, because of the underlying C implementation. See Why $'' or $'x0' is an empty string? Should be the null-character, isn't it?.



One option would be strip off the null bytes after the sort command, at the end of the pipeline using tr and store the result to solve the immediate problem of the warning message thrown. But that would still leave your logic flawed as the filenames with newlines would still be broken.



Use an array, use the mapfile or readarray command (on bash 4.4+) to directly slurp in the results from the find command



IFS= readarray -t -d '' samples < <(find . -type d -iregex './sample[0-9][0-9]' -printf "%f" | sort -z)





share|improve this answer

























  • Thank you. But would it not then be the same as using -printf "%fn"? If one are separating with newline in the result one are assuming there are no newlines in the data anyway (if you get what I mean). The whole point of using zero delimiter is to be sure one do not split names with newlines in them …

    – user3342816
    Jun 9 at 16:24











  • @user3342816: I thought your intention was to run the find command once, so after sorting the results, you wouldn't need the null delimited output anymore, so store the result in the variable without it

    – Inian
    Jun 9 at 16:27












  • From the link you posted (tried to find something like that first) I read it as it is not possible to store zero in a var, so that much set array to be the "only" option.

    – user3342816
    Jun 9 at 16:27











  • Yes. That was the intention. But if a value can have new-line, the result would be ambiguous even if sorted correctly.

    – user3342816
    Jun 9 at 16:29











  • @user3342816 : Then I suppose the readarray option is the one you want

    – Inian
    Jun 9 at 16:33













6












6








6







It is a fact that you can't store null bytes in a bash string context, because of the underlying C implementation. See Why $'' or $'x0' is an empty string? Should be the null-character, isn't it?.



One option would be strip off the null bytes after the sort command, at the end of the pipeline using tr and store the result to solve the immediate problem of the warning message thrown. But that would still leave your logic flawed as the filenames with newlines would still be broken.



Use an array, use the mapfile or readarray command (on bash 4.4+) to directly slurp in the results from the find command



IFS= readarray -t -d '' samples < <(find . -type d -iregex './sample[0-9][0-9]' -printf "%f" | sort -z)





share|improve this answer















It is a fact that you can't store null bytes in a bash string context, because of the underlying C implementation. See Why $'' or $'x0' is an empty string? Should be the null-character, isn't it?.



One option would be strip off the null bytes after the sort command, at the end of the pipeline using tr and store the result to solve the immediate problem of the warning message thrown. But that would still leave your logic flawed as the filenames with newlines would still be broken.



Use an array, use the mapfile or readarray command (on bash 4.4+) to directly slurp in the results from the find command



IFS= readarray -t -d '' samples < <(find . -type d -iregex './sample[0-9][0-9]' -printf "%f" | sort -z)






share|improve this answer














share|improve this answer



share|improve this answer








edited Jun 9 at 16:59

























answered Jun 9 at 16:14









InianInian

6,52517 silver badges34 bronze badges




6,52517 silver badges34 bronze badges












  • Thank you. But would it not then be the same as using -printf "%fn"? If one are separating with newline in the result one are assuming there are no newlines in the data anyway (if you get what I mean). The whole point of using zero delimiter is to be sure one do not split names with newlines in them …

    – user3342816
    Jun 9 at 16:24











  • @user3342816: I thought your intention was to run the find command once, so after sorting the results, you wouldn't need the null delimited output anymore, so store the result in the variable without it

    – Inian
    Jun 9 at 16:27












  • From the link you posted (tried to find something like that first) I read it as it is not possible to store zero in a var, so that much set array to be the "only" option.

    – user3342816
    Jun 9 at 16:27











  • Yes. That was the intention. But if a value can have new-line, the result would be ambiguous even if sorted correctly.

    – user3342816
    Jun 9 at 16:29











  • @user3342816 : Then I suppose the readarray option is the one you want

    – Inian
    Jun 9 at 16:33

















  • Thank you. But would it not then be the same as using -printf "%fn"? If one are separating with newline in the result one are assuming there are no newlines in the data anyway (if you get what I mean). The whole point of using zero delimiter is to be sure one do not split names with newlines in them …

    – user3342816
    Jun 9 at 16:24











  • @user3342816: I thought your intention was to run the find command once, so after sorting the results, you wouldn't need the null delimited output anymore, so store the result in the variable without it

    – Inian
    Jun 9 at 16:27












  • From the link you posted (tried to find something like that first) I read it as it is not possible to store zero in a var, so that much set array to be the "only" option.

    – user3342816
    Jun 9 at 16:27











  • Yes. That was the intention. But if a value can have new-line, the result would be ambiguous even if sorted correctly.

    – user3342816
    Jun 9 at 16:29











  • @user3342816 : Then I suppose the readarray option is the one you want

    – Inian
    Jun 9 at 16:33
















Thank you. But would it not then be the same as using -printf "%fn"? If one are separating with newline in the result one are assuming there are no newlines in the data anyway (if you get what I mean). The whole point of using zero delimiter is to be sure one do not split names with newlines in them …

– user3342816
Jun 9 at 16:24





Thank you. But would it not then be the same as using -printf "%fn"? If one are separating with newline in the result one are assuming there are no newlines in the data anyway (if you get what I mean). The whole point of using zero delimiter is to be sure one do not split names with newlines in them …

– user3342816
Jun 9 at 16:24













@user3342816: I thought your intention was to run the find command once, so after sorting the results, you wouldn't need the null delimited output anymore, so store the result in the variable without it

– Inian
Jun 9 at 16:27






@user3342816: I thought your intention was to run the find command once, so after sorting the results, you wouldn't need the null delimited output anymore, so store the result in the variable without it

– Inian
Jun 9 at 16:27














From the link you posted (tried to find something like that first) I read it as it is not possible to store zero in a var, so that much set array to be the "only" option.

– user3342816
Jun 9 at 16:27





From the link you posted (tried to find something like that first) I read it as it is not possible to store zero in a var, so that much set array to be the "only" option.

– user3342816
Jun 9 at 16:27













Yes. That was the intention. But if a value can have new-line, the result would be ambiguous even if sorted correctly.

– user3342816
Jun 9 at 16:29





Yes. That was the intention. But if a value can have new-line, the result would be ambiguous even if sorted correctly.

– user3342816
Jun 9 at 16:29













@user3342816 : Then I suppose the readarray option is the one you want

– Inian
Jun 9 at 16:33





@user3342816 : Then I suppose the readarray option is the one you want

– Inian
Jun 9 at 16:33













6














The bash shell does not support what you want to do. The zsh shell does out of the box.



% mkdir sample11 SAMple12 sample21 sample22 dir1
% ll
total 20
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 dir1
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 sample11
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 SAMple12
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 sample21
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 sample22
% samples=$(find . -type d -iregex './sample[0-9][0-9]' -print0 | sort -z)
% echo $samples
./sample11./SAMple12./sample21./sample22
% echo $samples | od -a
0000000 . / s a m p l e 1 1 nul . / S A M
0000020 p l e 1 2 nul . / s a m p l e 2 1
0000040 nul . / s a m p l e 2 2 nul nl
0000055
%





share|improve this answer




















  • 1





    ... however, please beware that the value of the environment variable samples will be truncated at the nul byte when being passed to child processes: If you perform export samples and start a child instance of zsh, $samples will only be ./sample11 in the child instance.

    – Martin Rosenau
    Jun 10 at 8:10















6














The bash shell does not support what you want to do. The zsh shell does out of the box.



% mkdir sample11 SAMple12 sample21 sample22 dir1
% ll
total 20
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 dir1
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 sample11
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 SAMple12
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 sample21
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 sample22
% samples=$(find . -type d -iregex './sample[0-9][0-9]' -print0 | sort -z)
% echo $samples
./sample11./SAMple12./sample21./sample22
% echo $samples | od -a
0000000 . / s a m p l e 1 1 nul . / S A M
0000020 p l e 1 2 nul . / s a m p l e 2 1
0000040 nul . / s a m p l e 2 2 nul nl
0000055
%





share|improve this answer




















  • 1





    ... however, please beware that the value of the environment variable samples will be truncated at the nul byte when being passed to child processes: If you perform export samples and start a child instance of zsh, $samples will only be ./sample11 in the child instance.

    – Martin Rosenau
    Jun 10 at 8:10













6












6








6







The bash shell does not support what you want to do. The zsh shell does out of the box.



% mkdir sample11 SAMple12 sample21 sample22 dir1
% ll
total 20
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 dir1
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 sample11
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 SAMple12
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 sample21
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 sample22
% samples=$(find . -type d -iregex './sample[0-9][0-9]' -print0 | sort -z)
% echo $samples
./sample11./SAMple12./sample21./sample22
% echo $samples | od -a
0000000 . / s a m p l e 1 1 nul . / S A M
0000020 p l e 1 2 nul . / s a m p l e 2 1
0000040 nul . / s a m p l e 2 2 nul nl
0000055
%





share|improve this answer















The bash shell does not support what you want to do. The zsh shell does out of the box.



% mkdir sample11 SAMple12 sample21 sample22 dir1
% ll
total 20
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 dir1
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 sample11
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 SAMple12
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 sample21
drwxrwxr-x 2 fpm fpm 4096 Jun 9 13:46 sample22
% samples=$(find . -type d -iregex './sample[0-9][0-9]' -print0 | sort -z)
% echo $samples
./sample11./SAMple12./sample21./sample22
% echo $samples | od -a
0000000 . / s a m p l e 1 1 nul . / S A M
0000020 p l e 1 2 nul . / s a m p l e 2 1
0000040 nul . / s a m p l e 2 2 nul nl
0000055
%






share|improve this answer














share|improve this answer



share|improve this answer








edited Jun 9 at 20:46









terdon

137k33 gold badges283 silver badges459 bronze badges




137k33 gold badges283 silver badges459 bronze badges










answered Jun 9 at 18:21









fpmurphyfpmurphy

2,53011 silver badges16 bronze badges




2,53011 silver badges16 bronze badges







  • 1





    ... however, please beware that the value of the environment variable samples will be truncated at the nul byte when being passed to child processes: If you perform export samples and start a child instance of zsh, $samples will only be ./sample11 in the child instance.

    – Martin Rosenau
    Jun 10 at 8:10












  • 1





    ... however, please beware that the value of the environment variable samples will be truncated at the nul byte when being passed to child processes: If you perform export samples and start a child instance of zsh, $samples will only be ./sample11 in the child instance.

    – Martin Rosenau
    Jun 10 at 8:10







1




1





... however, please beware that the value of the environment variable samples will be truncated at the nul byte when being passed to child processes: If you perform export samples and start a child instance of zsh, $samples will only be ./sample11 in the child instance.

– Martin Rosenau
Jun 10 at 8:10





... however, please beware that the value of the environment variable samples will be truncated at the nul byte when being passed to child processes: If you perform export samples and start a child instance of zsh, $samples will only be ./sample11 in the child instance.

– Martin Rosenau
Jun 10 at 8:10

















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.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f523855%2fnul-delimited-variable%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

Wikipedia:Vital articles Мазмуну Biography - Өмүр баян Philosophy and psychology - Философия жана психология Religion - Дин Social sciences - Коомдук илимдер Language and literature - Тил жана адабият Science - Илим Technology - Технология Arts and recreation - Искусство жана эс алуу History and geography - Тарых жана география Навигация менюсу

Bruxelas-Capital Índice Historia | Composición | Situación lingüística | Clima | Cidades irmandadas | Notas | Véxase tamén | Menú de navegacióneO uso das linguas en Bruxelas e a situación do neerlandés"Rexión de Bruxelas Capital"o orixinalSitio da rexiónPáxina de Bruselas no sitio da Oficina de Promoción Turística de Valonia e BruxelasMapa Interactivo da Rexión de Bruxelas-CapitaleeWorldCat332144929079854441105155190212ID28008674080552-90000 0001 0666 3698n94104302ID540940339365017018237

What should I write in an apology letter, since I have decided not to join a company after accepting an offer letterShould I keep looking after accepting a job offer?What should I do when I've been verbally told I would get an offer letter, but still haven't gotten one after 4 weeks?Do I accept an offer from a company that I am not likely to join?New job hasn't confirmed starting date and I want to give current employer as much notice as possibleHow should I address my manager in my resignation letter?HR delayed background verification, now jobless as resignedNo email communication after accepting a formal written offer. How should I phrase the call?What should I do if after receiving a verbal offer letter I am informed that my written job offer is put on hold due to some internal issues?Should I inform the current employer that I am about to resign within 1-2 weeks since I have signed the offer letter and waiting for visa?What company will do, if I send their offer letter to another company