[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Function visibility
From: |
Mike Frysinger |
Subject: |
Re: Function visibility |
Date: |
Mon, 1 Oct 2007 20:27:22 -0400 |
User-agent: |
KMail/1.9.7 |
On Monday 01 October 2007, retiredff wrote:
> I have several functions in my /etc/profile (Mac OSX 10.4.9). I can use the
> functions at the commandline, however inside of scripts I receive an error.
> I'll use an example of a function I have called cecho that echo's a string
> in a color that is passed in $2, $1 has the string:
>
> ./maintenance: line 27: cecho: command not found
>
> If I run this from the command line, it works fine. What am I doing wrong?
> I also have the same problem with any alias commands I use inside of
> scripts. If I type 'set' on the CLI it lists all of the functions.
scripts are not interactive shells so you wouldnt have the same environment as
an interactive shell ... so you need to place the definitions of functions
into a file and have the script source that at start
> Should I use export function-name?
that would only help when you executed the script from a shell which sourced
the /etc/profile and not if it were run through say a cronjob
-mike
signature.asc
Description: This is a digitally signed message part.
- Function visibility, retiredff, 2007/10/01
- Re: Function visibility,
Mike Frysinger <=
- Re: Function visibility, Stephane Chazelas, 2007/10/02
- Re: Function visibility, Bob Proulx, 2007/10/02
- Message not available
- Re: Function visibility, Stephane Chazelas, 2007/10/02
- Re: Function visibility, Bob Proulx, 2007/10/02
- Message not available
- Re: Function visibility, Stephane Chazelas, 2007/10/02
- Re: Function visibility, Matthew Woehlke, 2007/10/02
- Re: Function visibility, Bob Proulx, 2007/10/02