Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Sat, 21 Apr 2001 10:58:27 -0500 Message-ID: <3AE1AE23.C0B0304F@qwest.net> From: "AJ Reins" To: "Matthew O. Persico" Cc: "cygwin" X-Mailer: Mozilla 4.76 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 Subject: Re: ksh to bash question References: <3AE1034A DOT 5A7423BA AT acedsl DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "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 > sourced? > 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 needs. -- AJ Reins - tbispqwest.net -or- tbispmy-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