How to pass strange path arguments to commands












0















I'm sending commands via stdin, how can I send path arguments in a safe manner?



E.g.



stat /some strange/p"atnh'/


fails because of the strange path. Could path be stored in a variable or other means and have it work? Or is there an easy way to escape these strange paths before sending them?










share|improve this question







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.





















  • Could you explain more? Is /some strange/p"atnh'/ coming from a user argument? Is the second argument p"atnh containing a new line in the middle?

    – Inian
    6 mins ago
















0















I'm sending commands via stdin, how can I send path arguments in a safe manner?



E.g.



stat /some strange/p"atnh'/


fails because of the strange path. Could path be stored in a variable or other means and have it work? Or is there an easy way to escape these strange paths before sending them?










share|improve this question







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.





















  • Could you explain more? Is /some strange/p"atnh'/ coming from a user argument? Is the second argument p"atnh containing a new line in the middle?

    – Inian
    6 mins ago














0












0








0








I'm sending commands via stdin, how can I send path arguments in a safe manner?



E.g.



stat /some strange/p"atnh'/


fails because of the strange path. Could path be stored in a variable or other means and have it work? Or is there an easy way to escape these strange paths before sending them?










share|improve this question







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.












I'm sending commands via stdin, how can I send path arguments in a safe manner?



E.g.



stat /some strange/p"atnh'/


fails because of the strange path. Could path be stored in a variable or other means and have it work? Or is there an easy way to escape these strange paths before sending them?







bash shell-script shell






share|improve this question







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.











share|improve this question







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.









share|improve this question




share|improve this question






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 24 mins ago









TrevTheDevTrevTheDev

1083




1083




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.













  • Could you explain more? Is /some strange/p"atnh'/ coming from a user argument? Is the second argument p"atnh containing a new line in the middle?

    – Inian
    6 mins ago



















  • Could you explain more? Is /some strange/p"atnh'/ coming from a user argument? Is the second argument p"atnh containing a new line in the middle?

    – Inian
    6 mins ago

















Could you explain more? Is /some strange/p"atnh'/ coming from a user argument? Is the second argument p"atnh containing a new line in the middle?

– Inian
6 mins ago





Could you explain more? Is /some strange/p"atnh'/ coming from a user argument? Is the second argument p"atnh containing a new line in the middle?

– Inian
6 mins ago










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.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f504626%2fhow-to-pass-strange-path-arguments-to-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.










draft saved

draft discarded


















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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f504626%2fhow-to-pass-strange-path-arguments-to-commands%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

CARDNET

Boot-repair Failure: Unable to locate package grub-common:i386

Aws NAT - Aws IGW- Aws router