Using unusual paths with commands
Assuming one has the following directory:
mkdir """
'''n
"
And one queries the directory with:
stat --printf '%n' ** #or for simplicity stat --printf '%n' $'n''''\n$'n'
And captures the returned filename from stdout in a variable getting the correct binary representation of the filename:
#this should be a new line which I can't show
'''n
How can one send that variable to execute subsequent commands on stdin and have them ALWAYS work e.g. sending it as a string fails:
stat
'''n
This works for most cases but not all:
stat "/path/here"
The command below also works for most cases but not all:
p="$(cat<<EOF
'''n
EOF
)"
stat -- "$p"
If I use the captured variable as an arguement via node's spawn it works - so the capture from stat is correct and the problem is the translation that occurs when sending the variable as a string to stdin - which is required
bash shell-script shell node.js
edited 1 hour ago
Rui F Ribeiro
41.2k1481139
asked 1 hour ago
TrevTheDevTrevTheDev
1134
New contributor
TrevTheDev is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Assuming one has the following directory:
mkdir """
'''n
"
And one queries the directory with:
stat --printf '%n' ** #or for simplicity stat --printf '%n' $'n''''\n$'n'
And captures the returned filename from stdout in a variable getting the correct binary representation of the filename:
#this should be a new line which I can't show
'''n
How can one send that variable to execute subsequent commands on stdin and have them ALWAYS work e.g. sending it as a string fails:
stat
'''n
This works for most cases but not all:
stat "/path/here"
The command below also works for most cases but not all:
p="$(cat<<EOF
'''n
EOF
)"
stat -- "$p"
If I use the captured variable as an arguement via node's spawn it works - so the capture from stat is correct and the problem is the translation that occurs when sending the variable as a string to stdin - which is required
bash shell-script shell node.js
edited 1 hour ago
Rui F Ribeiro
41.2k1481139
asked 1 hour ago
TrevTheDevTrevTheDev
1134
New contributor
TrevTheDev is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
"the capture from stat is correct" ... I doubt that. If you used command substitution to get the output ofstat, like you did withcatand heredoc, then the trailing newline will be missing, because command substitution removes all trailing newlines.
– Olorin
52 mins ago
@Olorin - the stdout produced by stat is read into an array of bytes, transform into a string and then used to execute other commands. If the same command is sent using node.spawn("stat", [filename]) it works fine. However, when I send it spwn.stdin.write("stat ${filename}") it fails due to string translation of strange characters.
– TrevTheDev
18 mins ago
So this is about variables and capturing in nodejs? That looks like a nodejs programming problem and should be posted on Stack Overflow. At first I thought you were trying to capture output in a shell variable and somehow passing it on to nodejs.
– Olorin
4 mins ago
add a comment |
Assuming one has the following directory:
mkdir """
'''n
"
And one queries the directory with:
stat --printf '%n' ** #or for simplicity stat --printf '%n' $'n''''\n$'n'
And captures the returned filename from stdout in a variable getting the correct binary representation of the filename:
#this should be a new line which I can't show
'''n
How can one send that variable to execute subsequent commands on stdin and have them ALWAYS work e.g. sending it as a string fails:
stat
'''n
This works for most cases but not all:
stat "/path/here"
The command below also works for most cases but not all:
p="$(cat<<EOF
'''n
EOF
)"
stat -- "$p"
If I use the captured variable as an arguement via node's spawn it works - so the capture from stat is correct and the problem is the translation that occurs when sending the variable as a string to stdin - which is required
bash shell-script shell node.js
edited 1 hour ago
Rui F Ribeiro
41.2k1481139
asked 1 hour ago
TrevTheDevTrevTheDev
1134
New contributor
TrevTheDev is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Assuming one has the following directory:
mkdir """
'''n
"
And one queries the directory with:
stat --printf '%n' ** #or for simplicity stat --printf '%n' $'n''''\n$'n'
And captures the returned filename from stdout in a variable getting the correct binary representation of the filename:
#this should be a new line which I can't show
'''n
How can one send that variable to execute subsequent commands on stdin and have them ALWAYS work e.g. sending it as a string fails:
stat
'''n
This works for most cases but not all:
stat "/path/here"
The command below also works for most cases but not all:
p="$(cat<<EOF
'''n
EOF
)"
stat -- "$p"
If I use the captured variable as an arguement via node's spawn it works - so the capture from stat is correct and the problem is the translation that occurs when sending the variable as a string to stdin - which is required
bash shell-script shell node.js
bash shell-script shell node.js
edited 1 hour ago
Rui F Ribeiro
41.2k1481139
asked 1 hour ago
TrevTheDevTrevTheDev
1134
New contributor
TrevTheDev is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 1 hour ago
Rui F Ribeiro
41.2k1481139
asked 1 hour ago
TrevTheDevTrevTheDev
1134
New contributor
TrevTheDev is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 1 hour ago
Rui F Ribeiro
41.2k1481139
edited 1 hour ago
Rui F Ribeiro
41.2k1481139
edited 1 hour ago
Rui F Ribeiro
41.2k1481139
41.2k1481139
asked 1 hour ago
TrevTheDevTrevTheDev
1134
New contributor
TrevTheDev is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 1 hour ago
TrevTheDevTrevTheDev
1134
asked 1 hour ago
TrevTheDevTrevTheDev
1134
1134
New contributor
TrevTheDev is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
TrevTheDev is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
TrevTheDev is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
"the capture from stat is correct" ... I doubt that. If you used command substitution to get the output ofstat, like you did withcatand heredoc, then the trailing newline will be missing, because command substitution removes all trailing newlines.
– Olorin
52 mins ago
@Olorin - the stdout produced by stat is read into an array of bytes, transform into a string and then used to execute other commands. If the same command is sent using node.spawn("stat", [filename]) it works fine. However, when I send it spwn.stdin.write("stat ${filename}") it fails due to string translation of strange characters.
– TrevTheDev
18 mins ago
So this is about variables and capturing in nodejs? That looks like a nodejs programming problem and should be posted on Stack Overflow. At first I thought you were trying to capture output in a shell variable and somehow passing it on to nodejs.
– Olorin
4 mins ago
add a comment |
"the capture from stat is correct" ... I doubt that. If you used command substitution to get the output ofstat, like you did withcatand heredoc, then the trailing newline will be missing, because command substitution removes all trailing newlines.
– Olorin
52 mins ago
@Olorin - the stdout produced by stat is read into an array of bytes, transform into a string and then used to execute other commands. If the same command is sent using node.spawn("stat", [filename]) it works fine. However, when I send it spwn.stdin.write("stat ${filename}") it fails due to string translation of strange characters.
– TrevTheDev
18 mins ago
So this is about variables and capturing in nodejs? That looks like a nodejs programming problem and should be posted on Stack Overflow. At first I thought you were trying to capture output in a shell variable and somehow passing it on to nodejs.
– Olorin
4 mins ago
"the capture from stat is correct" ... I doubt that. If you used command substitution to get the output of
stat, like you did with cat and heredoc, then the trailing newline will be missing, because command substitution removes all trailing newlines.– Olorin
52 mins ago
"the capture from stat is correct" ... I doubt that. If you used command substitution to get the output of
stat, like you did with cat and heredoc, then the trailing newline will be missing, because command substitution removes all trailing newlines.– Olorin
52 mins ago
@Olorin - the stdout produced by stat is read into an array of bytes, transform into a string and then used to execute other commands. If the same command is sent using node.spawn("stat", [filename]) it works fine. However, when I send it spwn.stdin.write("stat ${filename}") it fails due to string translation of strange characters.
– TrevTheDev
18 mins ago
@Olorin - the stdout produced by stat is read into an array of bytes, transform into a string and then used to execute other commands. If the same command is sent using node.spawn("stat", [filename]) it works fine. However, when I send it spwn.stdin.write("stat ${filename}") it fails due to string translation of strange characters.
– TrevTheDev
18 mins ago
So this is about variables and capturing in nodejs? That looks like a nodejs programming problem and should be posted on Stack Overflow. At first I thought you were trying to capture output in a shell variable and somehow passing it on to nodejs.
– Olorin
4 mins ago
So this is about variables and capturing in nodejs? That looks like a nodejs programming problem and should be posted on Stack Overflow. At first I thought you were trying to capture output in a shell variable and somehow passing it on to nodejs.
– Olorin
4 mins 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
});
}
});
TrevTheDev is a new contributor. Be nice, and check out our Code of Conduct.
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%2f505043%2fusing-unusual-paths-with-commands%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
TrevTheDev is a new contributor. Be nice, and check out our Code of Conduct.
TrevTheDev is a new contributor. Be nice, and check out our Code of Conduct.
TrevTheDev is a new contributor. Be nice, and check out our Code of Conduct.
TrevTheDev is a new contributor. Be nice, and check out our Code of Conduct.
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%2f505043%2fusing-unusual-paths-with-commands%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
"the capture from stat is correct" ... I doubt that. If you used command substitution to get the output of
stat, like you did withcatand heredoc, then the trailing newline will be missing, because command substitution removes all trailing newlines.– Olorin
52 mins ago
@Olorin - the stdout produced by stat is read into an array of bytes, transform into a string and then used to execute other commands. If the same command is sent using node.spawn("stat", [filename]) it works fine. However, when I send it spwn.stdin.write("stat ${filename}") it fails due to string translation of strange characters.
– TrevTheDev
18 mins ago
So this is about variables and capturing in nodejs? That looks like a nodejs programming problem and should be posted on Stack Overflow. At first I thought you were trying to capture output in a shell variable and somehow passing it on to nodejs.
– Olorin
4 mins ago