How can I use command expansion on `` in `find -exec`?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I would like to find some directories via
find /path/to/a/dir -type d -links 2
and then for each pathname found by find
, assumed to be stored in variable pathname
, I would like to
stow -d "$(dirname "$pathname")" -t /home/t/bin "$(basename "$pathname")"
How can I combine the above with find -exec
, something similar to:
find /path/to/a/dir -type d -links 2 -exec stow -d "$(dirname )" -t /home/t/bin "$(basename )" ;
I think it doesn't work because the shell performs the command substitutions before running find
, and no pathname is found yet to replace in the command substitutions.
Thanks.
bash find command-substitution
add a comment |
up vote
0
down vote
favorite
I would like to find some directories via
find /path/to/a/dir -type d -links 2
and then for each pathname found by find
, assumed to be stored in variable pathname
, I would like to
stow -d "$(dirname "$pathname")" -t /home/t/bin "$(basename "$pathname")"
How can I combine the above with find -exec
, something similar to:
find /path/to/a/dir -type d -links 2 -exec stow -d "$(dirname )" -t /home/t/bin "$(basename )" ;
I think it doesn't work because the shell performs the command substitutions before running find
, and no pathname is found yet to replace in the command substitutions.
Thanks.
bash find command-substitution
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I would like to find some directories via
find /path/to/a/dir -type d -links 2
and then for each pathname found by find
, assumed to be stored in variable pathname
, I would like to
stow -d "$(dirname "$pathname")" -t /home/t/bin "$(basename "$pathname")"
How can I combine the above with find -exec
, something similar to:
find /path/to/a/dir -type d -links 2 -exec stow -d "$(dirname )" -t /home/t/bin "$(basename )" ;
I think it doesn't work because the shell performs the command substitutions before running find
, and no pathname is found yet to replace in the command substitutions.
Thanks.
bash find command-substitution
I would like to find some directories via
find /path/to/a/dir -type d -links 2
and then for each pathname found by find
, assumed to be stored in variable pathname
, I would like to
stow -d "$(dirname "$pathname")" -t /home/t/bin "$(basename "$pathname")"
How can I combine the above with find -exec
, something similar to:
find /path/to/a/dir -type d -links 2 -exec stow -d "$(dirname )" -t /home/t/bin "$(basename )" ;
I think it doesn't work because the shell performs the command substitutions before running find
, and no pathname is found yet to replace in the command substitutions.
Thanks.
bash find command-substitution
bash find command-substitution
asked Dec 2 at 3:53
Tim
25.3k72243447
25.3k72243447
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
You wrap it in a sh -c
command
find /path/to/dir -type d -links 2 -exec sh -c 'stow -d "$(dirname "$1")" -t /home/t/bin "$(basename "$1")"' sh ;
Thanks. Why do you usesh
instead ofbash
here?
– Tim
Dec 2 at 14:14
sh
is guaranteed to exist on any Unix system. Onlinux
,/bin/sh
is either a symlink to/bin/bash
itself (eg. rhel, centos) or to something smaller and faster (/bin/dash
on ubuntu and debian).
– mosvy
Dec 2 at 14:28
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
You wrap it in a sh -c
command
find /path/to/dir -type d -links 2 -exec sh -c 'stow -d "$(dirname "$1")" -t /home/t/bin "$(basename "$1")"' sh ;
Thanks. Why do you usesh
instead ofbash
here?
– Tim
Dec 2 at 14:14
sh
is guaranteed to exist on any Unix system. Onlinux
,/bin/sh
is either a symlink to/bin/bash
itself (eg. rhel, centos) or to something smaller and faster (/bin/dash
on ubuntu and debian).
– mosvy
Dec 2 at 14:28
add a comment |
up vote
2
down vote
accepted
You wrap it in a sh -c
command
find /path/to/dir -type d -links 2 -exec sh -c 'stow -d "$(dirname "$1")" -t /home/t/bin "$(basename "$1")"' sh ;
Thanks. Why do you usesh
instead ofbash
here?
– Tim
Dec 2 at 14:14
sh
is guaranteed to exist on any Unix system. Onlinux
,/bin/sh
is either a symlink to/bin/bash
itself (eg. rhel, centos) or to something smaller and faster (/bin/dash
on ubuntu and debian).
– mosvy
Dec 2 at 14:28
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
You wrap it in a sh -c
command
find /path/to/dir -type d -links 2 -exec sh -c 'stow -d "$(dirname "$1")" -t /home/t/bin "$(basename "$1")"' sh ;
You wrap it in a sh -c
command
find /path/to/dir -type d -links 2 -exec sh -c 'stow -d "$(dirname "$1")" -t /home/t/bin "$(basename "$1")"' sh ;
answered Dec 2 at 4:29
mosvy
5,1791323
5,1791323
Thanks. Why do you usesh
instead ofbash
here?
– Tim
Dec 2 at 14:14
sh
is guaranteed to exist on any Unix system. Onlinux
,/bin/sh
is either a symlink to/bin/bash
itself (eg. rhel, centos) or to something smaller and faster (/bin/dash
on ubuntu and debian).
– mosvy
Dec 2 at 14:28
add a comment |
Thanks. Why do you usesh
instead ofbash
here?
– Tim
Dec 2 at 14:14
sh
is guaranteed to exist on any Unix system. Onlinux
,/bin/sh
is either a symlink to/bin/bash
itself (eg. rhel, centos) or to something smaller and faster (/bin/dash
on ubuntu and debian).
– mosvy
Dec 2 at 14:28
Thanks. Why do you use
sh
instead of bash
here?– Tim
Dec 2 at 14:14
Thanks. Why do you use
sh
instead of bash
here?– Tim
Dec 2 at 14:14
sh
is guaranteed to exist on any Unix system. On linux
, /bin/sh
is either a symlink to /bin/bash
itself (eg. rhel, centos) or to something smaller and faster (/bin/dash
on ubuntu and debian).– mosvy
Dec 2 at 14:28
sh
is guaranteed to exist on any Unix system. On linux
, /bin/sh
is either a symlink to /bin/bash
itself (eg. rhel, centos) or to something smaller and faster (/bin/dash
on ubuntu and debian).– mosvy
Dec 2 at 14:28
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f485432%2fhow-can-i-use-command-expansion-on-in-find-exec%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