Use xargs to build and run a command list
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
How to use xargs to build and run a command list such as these:
#1
cmd1 <arg1> && cmd2 <arg1> && cmd3 <arg1>
#2
cmd1 <arg1> ; cmd2 <arg1>
xargs
asked Mar 14 at 11:53
Tran TrietTran Triet
12610
add a comment |
How to use xargs to build and run a command list such as these:
#1
cmd1 <arg1> && cmd2 <arg1> && cmd3 <arg1>
#2
cmd1 <arg1> ; cmd2 <arg1>
xargs
asked Mar 14 at 11:53
Tran TrietTran Triet
12610
add a comment |
How to use xargs to build and run a command list such as these:
#1
cmd1 <arg1> && cmd2 <arg1> && cmd3 <arg1>
#2
cmd1 <arg1> ; cmd2 <arg1>
xargs
asked Mar 14 at 11:53
Tran TrietTran Triet
12610
How to use xargs to build and run a command list such as these:
#1
cmd1 <arg1> && cmd2 <arg1> && cmd3 <arg1>
#2
cmd1 <arg1> ; cmd2 <arg1>
xargs
xargs
asked Mar 14 at 11:53
Tran TrietTran Triet
12610
asked Mar 14 at 11:53
Tran TrietTran Triet
12610
asked Mar 14 at 11:53
Tran TrietTran Triet
12610
asked Mar 14 at 11:53
Tran TrietTran Triet
12610
asked Mar 14 at 11:53
Tran TrietTran Triet
12610
12610
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
By starting a child shell for each line of input to xargs:
xargs -I sh -c 'cmd1 "$1" && cmd2 "$1" && cmd3 "$1"' sh
xargs -I sh -c 'cmd1 "$1"; cmd2 "$1"' sh
This runs sh -c which executes the given string as a shell script. The arguments to sh -c, after the script itself, are given to $0 and $1 inside the script. The value of $0 should usually be the name of the shell, which is why we pass sh as this argument (it will be used in error messages).
Alternatively,
xargs sh -c '
for arg do
cmd1 "$arg" && cmd2 "$arg" && cmd3 "$arg"
done' sh
xargs sh -c '
for arg do
cmd1 "$arg"
cmd2 "$arg"
done' sh
These variations will take as many arguments as possible and then apply the code to these in a loop inside the sh -c scripts.
As always when using xargs, care must be taken so that the arguments supplied to the given utility (sh -c here) are delimited properly.
answered Mar 14 at 11:57
Kusalananda♦Kusalananda
141k17263439
I'm actually using this method, but I wonder if there's any other ways that are more xargs native.
– Tran Triet
Mar 14 at 11:59
1
@TranTriet No, not really. This is a fairly common way of doing it. What are your issues with this way of doing it?
– Kusalananda♦
Mar 14 at 12:03
@TranTriet See updated answer.
– Kusalananda♦
Mar 14 at 12:08
add a comment |
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%2f506265%2fuse-xargs-to-build-and-run-a-command-list%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
By starting a child shell for each line of input to xargs:
xargs -I sh -c 'cmd1 "$1" && cmd2 "$1" && cmd3 "$1"' sh
xargs -I sh -c 'cmd1 "$1"; cmd2 "$1"' sh
This runs sh -c which executes the given string as a shell script. The arguments to sh -c, after the script itself, are given to $0 and $1 inside the script. The value of $0 should usually be the name of the shell, which is why we pass sh as this argument (it will be used in error messages).
Alternatively,
xargs sh -c '
for arg do
cmd1 "$arg" && cmd2 "$arg" && cmd3 "$arg"
done' sh
xargs sh -c '
for arg do
cmd1 "$arg"
cmd2 "$arg"
done' sh
These variations will take as many arguments as possible and then apply the code to these in a loop inside the sh -c scripts.
As always when using xargs, care must be taken so that the arguments supplied to the given utility (sh -c here) are delimited properly.
answered Mar 14 at 11:57
Kusalananda♦Kusalananda
141k17263439
I'm actually using this method, but I wonder if there's any other ways that are more xargs native.
– Tran Triet
Mar 14 at 11:59
1
@TranTriet No, not really. This is a fairly common way of doing it. What are your issues with this way of doing it?
– Kusalananda♦
Mar 14 at 12:03
@TranTriet See updated answer.
– Kusalananda♦
Mar 14 at 12:08
add a comment |
By starting a child shell for each line of input to xargs:
xargs -I sh -c 'cmd1 "$1" && cmd2 "$1" && cmd3 "$1"' sh
xargs -I sh -c 'cmd1 "$1"; cmd2 "$1"' sh
This runs sh -c which executes the given string as a shell script. The arguments to sh -c, after the script itself, are given to $0 and $1 inside the script. The value of $0 should usually be the name of the shell, which is why we pass sh as this argument (it will be used in error messages).
Alternatively,
xargs sh -c '
for arg do
cmd1 "$arg" && cmd2 "$arg" && cmd3 "$arg"
done' sh
xargs sh -c '
for arg do
cmd1 "$arg"
cmd2 "$arg"
done' sh
These variations will take as many arguments as possible and then apply the code to these in a loop inside the sh -c scripts.
As always when using xargs, care must be taken so that the arguments supplied to the given utility (sh -c here) are delimited properly.
answered Mar 14 at 11:57
Kusalananda♦Kusalananda
141k17263439
I'm actually using this method, but I wonder if there's any other ways that are more xargs native.
– Tran Triet
Mar 14 at 11:59
1
@TranTriet No, not really. This is a fairly common way of doing it. What are your issues with this way of doing it?
– Kusalananda♦
Mar 14 at 12:03
@TranTriet See updated answer.
– Kusalananda♦
Mar 14 at 12:08
add a comment |
By starting a child shell for each line of input to xargs:
xargs -I sh -c 'cmd1 "$1" && cmd2 "$1" && cmd3 "$1"' sh
xargs -I sh -c 'cmd1 "$1"; cmd2 "$1"' sh
This runs sh -c which executes the given string as a shell script. The arguments to sh -c, after the script itself, are given to $0 and $1 inside the script. The value of $0 should usually be the name of the shell, which is why we pass sh as this argument (it will be used in error messages).
Alternatively,
xargs sh -c '
for arg do
cmd1 "$arg" && cmd2 "$arg" && cmd3 "$arg"
done' sh
xargs sh -c '
for arg do
cmd1 "$arg"
cmd2 "$arg"
done' sh
These variations will take as many arguments as possible and then apply the code to these in a loop inside the sh -c scripts.
As always when using xargs, care must be taken so that the arguments supplied to the given utility (sh -c here) are delimited properly.
answered Mar 14 at 11:57
Kusalananda♦Kusalananda
141k17263439
By starting a child shell for each line of input to xargs:
xargs -I sh -c 'cmd1 "$1" && cmd2 "$1" && cmd3 "$1"' sh
xargs -I sh -c 'cmd1 "$1"; cmd2 "$1"' sh
This runs sh -c which executes the given string as a shell script. The arguments to sh -c, after the script itself, are given to $0 and $1 inside the script. The value of $0 should usually be the name of the shell, which is why we pass sh as this argument (it will be used in error messages).
Alternatively,
xargs sh -c '
for arg do
cmd1 "$arg" && cmd2 "$arg" && cmd3 "$arg"
done' sh
xargs sh -c '
for arg do
cmd1 "$arg"
cmd2 "$arg"
done' sh
These variations will take as many arguments as possible and then apply the code to these in a loop inside the sh -c scripts.
As always when using xargs, care must be taken so that the arguments supplied to the given utility (sh -c here) are delimited properly.
answered Mar 14 at 11:57
Kusalananda♦Kusalananda
141k17263439
edited Mar 14 at 12:08
answered Mar 14 at 11:57
Kusalananda♦Kusalananda
141k17263439
answered Mar 14 at 11:57
Kusalananda♦Kusalananda
141k17263439
answered Mar 14 at 11:57
Kusalananda♦Kusalananda
141k17263439
141k17263439
I'm actually using this method, but I wonder if there's any other ways that are more xargs native.
– Tran Triet
Mar 14 at 11:59
1
@TranTriet No, not really. This is a fairly common way of doing it. What are your issues with this way of doing it?
– Kusalananda♦
Mar 14 at 12:03
@TranTriet See updated answer.
– Kusalananda♦
Mar 14 at 12:08
add a comment |
I'm actually using this method, but I wonder if there's any other ways that are more xargs native.
– Tran Triet
Mar 14 at 11:59
1
@TranTriet No, not really. This is a fairly common way of doing it. What are your issues with this way of doing it?
– Kusalananda♦
Mar 14 at 12:03
@TranTriet See updated answer.
– Kusalananda♦
Mar 14 at 12:08
I'm actually using this method, but I wonder if there's any other ways that are more xargs native.
– Tran Triet
Mar 14 at 11:59
I'm actually using this method, but I wonder if there's any other ways that are more xargs native.
– Tran Triet
Mar 14 at 11:59
1
1
@TranTriet No, not really. This is a fairly common way of doing it. What are your issues with this way of doing it?
– Kusalananda♦
Mar 14 at 12:03
@TranTriet No, not really. This is a fairly common way of doing it. What are your issues with this way of doing it?
– Kusalananda♦
Mar 14 at 12:03
@TranTriet See updated answer.
– Kusalananda♦
Mar 14 at 12:08
@TranTriet See updated answer.
– Kusalananda♦
Mar 14 at 12:08
add a comment |
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%2f506265%2fuse-xargs-to-build-and-run-a-command-list%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