Working with strange filenames
How can the script below be made to always work no matter the filenames returned by find ?
#!/bin/sh
cmds_should_always_work() {
echo "nn*********************************" $1
stat --printf='%n' -- "$1" || echo STATFAILED
echo "n----------------n"
lsattr -d -- "$1" || echo LSATTRFAILED
echo "n----------------n"
};
for item in $(find "$1" -maxdepth 1 -mindepth 1); do cmds_should_always_work "${item}"; done
For example files in the find directory that contain a new line break this script.
Further if the find directory is named e.g. $schema, this script returns the parent directory. How can this be avoided by the script vs. having to supply and escaped path somepath/$schema to the script?
shell-script shell
add a comment |
How can the script below be made to always work no matter the filenames returned by find ?
#!/bin/sh
cmds_should_always_work() {
echo "nn*********************************" $1
stat --printf='%n' -- "$1" || echo STATFAILED
echo "n----------------n"
lsattr -d -- "$1" || echo LSATTRFAILED
echo "n----------------n"
};
for item in $(find "$1" -maxdepth 1 -mindepth 1); do cmds_should_always_work "${item}"; done
For example files in the find directory that contain a new line break this script.
Further if the find directory is named e.g. $schema, this script returns the parent directory. How can this be avoided by the script vs. having to supply and escaped path somepath/$schema to the script?
shell-script shell
2
Try to useexec
option of find instead offor
loop.
– Prvt_Yadv
3 hours ago
2
The options are pretty much covered in Why is looping over find's output bad practice?
– steeldriver
3 hours ago
add a comment |
How can the script below be made to always work no matter the filenames returned by find ?
#!/bin/sh
cmds_should_always_work() {
echo "nn*********************************" $1
stat --printf='%n' -- "$1" || echo STATFAILED
echo "n----------------n"
lsattr -d -- "$1" || echo LSATTRFAILED
echo "n----------------n"
};
for item in $(find "$1" -maxdepth 1 -mindepth 1); do cmds_should_always_work "${item}"; done
For example files in the find directory that contain a new line break this script.
Further if the find directory is named e.g. $schema, this script returns the parent directory. How can this be avoided by the script vs. having to supply and escaped path somepath/$schema to the script?
shell-script shell
How can the script below be made to always work no matter the filenames returned by find ?
#!/bin/sh
cmds_should_always_work() {
echo "nn*********************************" $1
stat --printf='%n' -- "$1" || echo STATFAILED
echo "n----------------n"
lsattr -d -- "$1" || echo LSATTRFAILED
echo "n----------------n"
};
for item in $(find "$1" -maxdepth 1 -mindepth 1); do cmds_should_always_work "${item}"; done
For example files in the find directory that contain a new line break this script.
Further if the find directory is named e.g. $schema, this script returns the parent directory. How can this be avoided by the script vs. having to supply and escaped path somepath/$schema to the script?
shell-script shell
shell-script shell
asked 3 hours ago
TrevTheDevTrevTheDev
1154
1154
2
Try to useexec
option of find instead offor
loop.
– Prvt_Yadv
3 hours ago
2
The options are pretty much covered in Why is looping over find's output bad practice?
– steeldriver
3 hours ago
add a comment |
2
Try to useexec
option of find instead offor
loop.
– Prvt_Yadv
3 hours ago
2
The options are pretty much covered in Why is looping over find's output bad practice?
– steeldriver
3 hours ago
2
2
Try to use
exec
option of find instead of for
loop.– Prvt_Yadv
3 hours ago
Try to use
exec
option of find instead of for
loop.– Prvt_Yadv
3 hours ago
2
2
The options are pretty much covered in Why is looping over find's output bad practice?
– steeldriver
3 hours ago
The options are pretty much covered in Why is looping over find's output bad practice?
– steeldriver
3 hours ago
add a comment |
0
active
oldest
votes
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%2f506196%2fworking-with-strange-filenames%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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%2f506196%2fworking-with-strange-filenames%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
Try to use
exec
option of find instead offor
loop.– Prvt_Yadv
3 hours ago
2
The options are pretty much covered in Why is looping over find's output bad practice?
– steeldriver
3 hours ago