set -f inside function












0















I have a directory with files file1.c, file2.c and file3.c. The output of find is:



$ find -name "*.c"
./file1.c
./file2.c
./file3.c


I want to remove the quotes from the argument of -name. So I use set -f:



 $ set -f
$ find -name *.c
./file1.c
./file2.c
./file3.c
$ set +f


Since this worked as expected I made a function in .bashrc based on the previous code:



find() {
set -f
eval command find $@
set +f
}


but testing it gave the error:



$ . ~/.bashrc && find -name *c
find: paths must precede expression: file1.c
Usage: find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec] [path...] [expression


Why did set -f; find -name *.c ; set +f give error when calling the function, but did not give error when entering the commands in the shell?










share|improve this question























  • Remove eval, and use "$(command -v find)" "$@"

    – cuonglm
    6 mins ago











  • I follow your suggestion but the function does not output any text and I have to stop with Ctrl+C

    – Sergio
    just now
















0















I have a directory with files file1.c, file2.c and file3.c. The output of find is:



$ find -name "*.c"
./file1.c
./file2.c
./file3.c


I want to remove the quotes from the argument of -name. So I use set -f:



 $ set -f
$ find -name *.c
./file1.c
./file2.c
./file3.c
$ set +f


Since this worked as expected I made a function in .bashrc based on the previous code:



find() {
set -f
eval command find $@
set +f
}


but testing it gave the error:



$ . ~/.bashrc && find -name *c
find: paths must precede expression: file1.c
Usage: find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec] [path...] [expression


Why did set -f; find -name *.c ; set +f give error when calling the function, but did not give error when entering the commands in the shell?










share|improve this question























  • Remove eval, and use "$(command -v find)" "$@"

    – cuonglm
    6 mins ago











  • I follow your suggestion but the function does not output any text and I have to stop with Ctrl+C

    – Sergio
    just now














0












0








0








I have a directory with files file1.c, file2.c and file3.c. The output of find is:



$ find -name "*.c"
./file1.c
./file2.c
./file3.c


I want to remove the quotes from the argument of -name. So I use set -f:



 $ set -f
$ find -name *.c
./file1.c
./file2.c
./file3.c
$ set +f


Since this worked as expected I made a function in .bashrc based on the previous code:



find() {
set -f
eval command find $@
set +f
}


but testing it gave the error:



$ . ~/.bashrc && find -name *c
find: paths must precede expression: file1.c
Usage: find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec] [path...] [expression


Why did set -f; find -name *.c ; set +f give error when calling the function, but did not give error when entering the commands in the shell?










share|improve this question














I have a directory with files file1.c, file2.c and file3.c. The output of find is:



$ find -name "*.c"
./file1.c
./file2.c
./file3.c


I want to remove the quotes from the argument of -name. So I use set -f:



 $ set -f
$ find -name *.c
./file1.c
./file2.c
./file3.c
$ set +f


Since this worked as expected I made a function in .bashrc based on the previous code:



find() {
set -f
eval command find $@
set +f
}


but testing it gave the error:



$ . ~/.bashrc && find -name *c
find: paths must precede expression: file1.c
Usage: find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec] [path...] [expression


Why did set -f; find -name *.c ; set +f give error when calling the function, but did not give error when entering the commands in the shell?







bash find function set






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 11 mins ago









SergioSergio

1014




1014













  • Remove eval, and use "$(command -v find)" "$@"

    – cuonglm
    6 mins ago











  • I follow your suggestion but the function does not output any text and I have to stop with Ctrl+C

    – Sergio
    just now



















  • Remove eval, and use "$(command -v find)" "$@"

    – cuonglm
    6 mins ago











  • I follow your suggestion but the function does not output any text and I have to stop with Ctrl+C

    – Sergio
    just now

















Remove eval, and use "$(command -v find)" "$@"

– cuonglm
6 mins ago





Remove eval, and use "$(command -v find)" "$@"

– cuonglm
6 mins ago













I follow your suggestion but the function does not output any text and I have to stop with Ctrl+C

– Sergio
just now





I follow your suggestion but the function does not output any text and I have to stop with Ctrl+C

– Sergio
just now










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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f500085%2fset-f-inside-function%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
















draft saved

draft discarded




















































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%2f500085%2fset-f-inside-function%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

Entries order in /etc/network/interfaces

新発田市

Grub takes very long (several minutes) to open Menu (in Multi-Boot-System)