Suppose I have bash_functions.sh:

function test(){

function test2(){

And in my ~/.bashrc I do:

source ~/bash_functions.sh

Is it possible to, when sourcing it, avoid sourcing a specific function? I mean, source everything in bash_functions.sh, except for test?

  • 2
    @Somebody: Perhaps you could elaborate on your use case? What are you trying to do here? – Faheem Mitha Mar 20 '11 at 8:58
  • Sometimes you're using bash_functions.sh from someone, and want everything there's there except for a few functions that you already have defined in your own files and don't want them overriden. – Somebody still uses you MS-DOS Mar 20 '11 at 15:36
  • @Somebody: couldn't you just comment out the ones you don't want? – Faheem Mitha Mar 20 '11 at 15:38
  • @Faheem Mitha: this becomes unpractical over time if you use a bash_functions.sh that is versioned somewhere, and always do a checkout/pull from it. – Somebody still uses you MS-DOS Mar 20 '11 at 16:13
  • @Somebody: Ok. I see. I guess keeping your diffs local and merging with upstream is not an option then? – Faheem Mitha Mar 20 '11 at 20:11

In a function definition foo () { … }, if foo is an alias, it is expanded. This can sometimes be a problem, but here it helps. Alias foo to some other name before sourcing the file, and you'll be defining a different function. In bash, alias expansion is off by default in non-interactive shells, so you need to turn it on with shopt -s expand_aliases.

If sourced.sh contains

foo () {
  echo "foo from sourced.sh"

then you use it this way

foo () {
  echo "old foo"
shopt -s expand_aliases   # necessary in bash; just skip in ash/ksh/zsh
alias foo=do_not_define_foo
. sourced.sh
unalias foo; unset -f do_not_define_foo

then you get old foo. Note that the sourced file must use the foo () { … } function definition syntax, not function foo { … }, because the function keyword would block alias expansion.

| improve this answer | |
  • This seems to be an interesting approach, but I need the sourced scripts to be in the same foo () { ... } definition, right? I was thinking about putting all function names I didn't want to source in an array, and somehow "source" receive it and don't source them. Well, I think it's not going to be possible. Interesting hack, anyways! – Somebody still uses you MS-DOS Mar 25 '11 at 1:06
  • @Somebody: I don't understand your comment. The function definitions need to be in the portable foo () form and not in the ksh extension function foo form, but other than that you can effectively re-route any number of function definitions. – Gilles 'SO- stop being evil' Mar 25 '11 at 7:53

Not exactly, however, you can override the test() function. The last function definition always takes precedence. So if you source a file that has test() then define a function with the same name after that, the latter function will override the one that was sourced. I take advantage of this to provide some object-orientedness in some of my scripts.



    echo "This is the test function from bash_functions."
    echo "This is the test2 function from bash_functions."


    #this is thrown in just to show what happens in
    #the other direction
    echo "This is the test2 function from scripty."

source bash_functions.sh

    echo "This is the test1 function from scripty."


At the command line:

$ ./scripty_scripterson.sh 
This is the test1 function from scripty.
This is the test2 function from bash_functions.
| improve this answer | |
  • I'm already doing this approach. :) But somehow it seens wrong to me, and in my use case, I have to soure my files, source the external bash_functions.sh and again source my files (since I use some functions from my files when sourcing bash_functions.sh) – Somebody still uses you MS-DOS Mar 20 '11 at 16:16

You may create a temp-file, read it in, and delete it afterwards. To delete function 'test', I assume here that there is no '}' inside the function.

sed '/test()/,/}/d' testrc > ./tmprc && source ./tmprc && rm tmprc
| improve this answer | |

That's not possible. You can divide bash_functions.sh into 2 file, one include what you want to source, and another include the functions you don't want to source. and use a 3rd script file to combine them for normal usage.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.