Usage of enclosing braces {} as arguments to commands and their options












0















Examples



I've recently found examples of using pairs of enclosing braces {}, with nothing in between the opening and closing braces, as arguments to commands and even to their options:



cat foo | xargs -I{} echo {}



find . -size 0 -exec rm -i {} ;



No Documentation



My problem is that I cannot find a documentation in the GNU Bash Manual that describes the usage of {} in such context as in the examples above.



I do not think it is a parameter expansion, because a dollar sign must precede the enclosing braces in a parameter expansion as in ${}.



It cannot be a brace expansion either, because it takes the form of {x..y[..incr]}, where x and y are not optional.



It also cannot be a command grouping either, because {} is used as arguments.



Questions




  1. What does a pair of enclosing braces {} even mean, in general, as an argument to any command that accepts it?


  2. Where can I find a documentation that describes the usage of {} as arguments?










share







New contributor




Niko Gambt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Some commands have this options {} - meaning targets to act on, with find command, it's remove/rm found files.

    – Tuyen Pham
    25 secs ago
















0















Examples



I've recently found examples of using pairs of enclosing braces {}, with nothing in between the opening and closing braces, as arguments to commands and even to their options:



cat foo | xargs -I{} echo {}



find . -size 0 -exec rm -i {} ;



No Documentation



My problem is that I cannot find a documentation in the GNU Bash Manual that describes the usage of {} in such context as in the examples above.



I do not think it is a parameter expansion, because a dollar sign must precede the enclosing braces in a parameter expansion as in ${}.



It cannot be a brace expansion either, because it takes the form of {x..y[..incr]}, where x and y are not optional.



It also cannot be a command grouping either, because {} is used as arguments.



Questions




  1. What does a pair of enclosing braces {} even mean, in general, as an argument to any command that accepts it?


  2. Where can I find a documentation that describes the usage of {} as arguments?










share







New contributor




Niko Gambt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Some commands have this options {} - meaning targets to act on, with find command, it's remove/rm found files.

    – Tuyen Pham
    25 secs ago














0












0








0








Examples



I've recently found examples of using pairs of enclosing braces {}, with nothing in between the opening and closing braces, as arguments to commands and even to their options:



cat foo | xargs -I{} echo {}



find . -size 0 -exec rm -i {} ;



No Documentation



My problem is that I cannot find a documentation in the GNU Bash Manual that describes the usage of {} in such context as in the examples above.



I do not think it is a parameter expansion, because a dollar sign must precede the enclosing braces in a parameter expansion as in ${}.



It cannot be a brace expansion either, because it takes the form of {x..y[..incr]}, where x and y are not optional.



It also cannot be a command grouping either, because {} is used as arguments.



Questions




  1. What does a pair of enclosing braces {} even mean, in general, as an argument to any command that accepts it?


  2. Where can I find a documentation that describes the usage of {} as arguments?










share







New contributor




Niko Gambt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












Examples



I've recently found examples of using pairs of enclosing braces {}, with nothing in between the opening and closing braces, as arguments to commands and even to their options:



cat foo | xargs -I{} echo {}



find . -size 0 -exec rm -i {} ;



No Documentation



My problem is that I cannot find a documentation in the GNU Bash Manual that describes the usage of {} in such context as in the examples above.



I do not think it is a parameter expansion, because a dollar sign must precede the enclosing braces in a parameter expansion as in ${}.



It cannot be a brace expansion either, because it takes the form of {x..y[..incr]}, where x and y are not optional.



It also cannot be a command grouping either, because {} is used as arguments.



Questions




  1. What does a pair of enclosing braces {} even mean, in general, as an argument to any command that accepts it?


  2. Where can I find a documentation that describes the usage of {} as arguments?








bash shell





share







New contributor




Niko Gambt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.










share







New contributor




Niko Gambt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








share



share






New contributor




Niko Gambt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 4 mins ago









Niko GambtNiko Gambt

1




1




New contributor




Niko Gambt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Niko Gambt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Niko Gambt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • Some commands have this options {} - meaning targets to act on, with find command, it's remove/rm found files.

    – Tuyen Pham
    25 secs ago



















  • Some commands have this options {} - meaning targets to act on, with find command, it's remove/rm found files.

    – Tuyen Pham
    25 secs ago

















Some commands have this options {} - meaning targets to act on, with find command, it's remove/rm found files.

– Tuyen Pham
25 secs ago





Some commands have this options {} - meaning targets to act on, with find command, it's remove/rm found files.

– Tuyen Pham
25 secs 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
});


}
});






Niko Gambt 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%2f494526%2fusage-of-enclosing-braces-as-arguments-to-commands-and-their-options%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








Niko Gambt is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















Niko Gambt is a new contributor. Be nice, and check out our Code of Conduct.













Niko Gambt is a new contributor. Be nice, and check out our Code of Conduct.












Niko Gambt 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%2f494526%2fusage-of-enclosing-braces-as-arguments-to-commands-and-their-options%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

濃尾地震