This is the mail archive of the
mailing list for the Cygwin project.
Re: ksh to bash question
- To: "Matthew O. Persico" <persicom at acedsl dot com>
- Subject: Re: ksh to bash question
- From: "AJ Reins" <tbisp at qwest dot net>
- Date: Sat, 21 Apr 2001 10:58:27 -0500
- Cc: "cygwin" <cygwin at cygwin dot com>
- References: <3AE1034A.5A7423BA@acedsl.com>
"Matthew O. Persico" wrote:
> Not exactly a cygwin question, but since I am converting to Cygwin...
> In KSH, you could take each shell function, put it in its own file, set
> the FPATH envvar to point where the files are and then invoke functions.
> The first time the function is called, the FPATH is searched. If the
> file is found is is sourced and executed. Subsequent invokations are
> merely executed.
> In BASH, does one have to explicitly source all functions before first
> use or does FPATH (or its equivilent) exist? If not, where are functions
> traditionally stored and where (.bash_profile, .bashrc, etc) are they
This is not built into Bash, however, in the examples directory of the
source distribution are many examples of scripts. Including one named
require.bash in the scripts.noah subdirectory. In all there are about
400K of examples in those subdirectories. One or more should fit your
AJ Reins - tbisp<AT>qwest.net -or- tbisp<AT>my-deja.com
Warning label I would like to see on software:
"Before using, read instructions.
If you do not understand or cannot read,
do no use this product."
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple