On Wed, Nov 11, 2009 at 01:19:30AM +, James Laver said:
Perhaps I'm overlooking something obvious, but why don't you just parse twice?
Because I don't know where the config file is until I parse the command
line options.
I could
getArgs
. ${config_file}
getArgs
but I think Bash getopts
I have a small problem in that I'm trying to modify a bash script so
that currently does this
. config
# then inspect command line args
getArgs
so that you can specify the config file on the command line. Which
necessarily requires do
config_file=config
# inspect command
On Wed, Nov 11, 2009 at 01:03:08AM +, me said:
Is there an easy way to say source this config file but don't override
any variable already set? or some sort of standard recipe? Or amy I
going to have to write something that reads the config file line by
line, splits out any variable
On Wed, Nov 11, 2009 at 1:03 AM, Simon Wistow si...@thegestalt.org wrote:
I have a small problem in that I'm trying to modify a bash script so
that currently does this
. config
# then inspect command line args
getArgs
so that you can specify the config file on the command line.
On 11 Nov 2009, at 01:03, Simon Wistow wrote:
I have a small problem in that I'm trying to modify a bash script so
that currently does this
. config
# then inspect command line args
getArgs
so that you can specify the config file on the command line. Which
necessarily requires do
