Distinguish a command not a native second transmitter
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
This question might be frivolous but it is haunting me long.
suppose
[root@iz2ze9wve43n2nyuvmsfx5z /]# find . -maxdepth 2 -type d | ls
bin dev home lib64 media opt root sbin sys usr
boot etc lib lost+found mnt proc run srv tmp var
ls did nothing, as a rescue I should reconstruct them to a list to ls
find . -type d | xargs ls
#millions of outputs
However, grep does a good job
[root@iz2ze9wve43n2nyuvmsfx5z /]# find . -maxdepth 2 -type d | grep home
./home
How could I distinguish a command was not born as a second transmitter from underly understanding rather than trying, error test and remember.
bash
add a comment |Â
up vote
0
down vote
favorite
This question might be frivolous but it is haunting me long.
suppose
[root@iz2ze9wve43n2nyuvmsfx5z /]# find . -maxdepth 2 -type d | ls
bin dev home lib64 media opt root sbin sys usr
boot etc lib lost+found mnt proc run srv tmp var
ls did nothing, as a rescue I should reconstruct them to a list to ls
find . -type d | xargs ls
#millions of outputs
However, grep does a good job
[root@iz2ze9wve43n2nyuvmsfx5z /]# find . -maxdepth 2 -type d | grep home
./home
How could I distinguish a command was not born as a second transmitter from underly understanding rather than trying, error test and remember.
bash
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
This question might be frivolous but it is haunting me long.
suppose
[root@iz2ze9wve43n2nyuvmsfx5z /]# find . -maxdepth 2 -type d | ls
bin dev home lib64 media opt root sbin sys usr
boot etc lib lost+found mnt proc run srv tmp var
ls did nothing, as a rescue I should reconstruct them to a list to ls
find . -type d | xargs ls
#millions of outputs
However, grep does a good job
[root@iz2ze9wve43n2nyuvmsfx5z /]# find . -maxdepth 2 -type d | grep home
./home
How could I distinguish a command was not born as a second transmitter from underly understanding rather than trying, error test and remember.
bash
This question might be frivolous but it is haunting me long.
suppose
[root@iz2ze9wve43n2nyuvmsfx5z /]# find . -maxdepth 2 -type d | ls
bin dev home lib64 media opt root sbin sys usr
boot etc lib lost+found mnt proc run srv tmp var
ls did nothing, as a rescue I should reconstruct them to a list to ls
find . -type d | xargs ls
#millions of outputs
However, grep does a good job
[root@iz2ze9wve43n2nyuvmsfx5z /]# find . -maxdepth 2 -type d | grep home
./home
How could I distinguish a command was not born as a second transmitter from underly understanding rather than trying, error test and remember.
bash
bash
asked 1 min ago
Sawajiri
3206
3206
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f480019%2fdistinguish-a-command-not-a-native-second-transmitter%23new-answer', 'question_page');
);
Post as a guest
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
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
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