Current menu script

[Jeff Harrison]

--- Fairlight <fairlite at fairlite.com> wrote:

> Confusious (Ken Cole) say:
> > 
> > Mark,
> > 
> > > It would be far more versatile to parse the
> fppath file to
> > > obtain the path.  This way, in future, if and
> when you need
> > > to migrate systems or even just change the
> location of fP's
> > > programs to elsewhence, you don't have to modify
> anything
> > > except the actual file that needs changing
> anyway.
> > 
> > I think he meant the menu path that the user has
> taken to get to the
> > menu from which the script has been called, not a
> directory path.
> 
> Okay, let's revisit:
> 
> With neither thought nor caution, Jeff Harrison
> blurted:
> >
> > Perhaps I was not clear.  I was modifying all of
> the
> > shell scripts anyway - by adding the following
> line as
> > the first thing in each script:
> >
> > /appl/fp/dclerk lib -s1 -z logger -rw $0
> 
> No matter what his intent, that's a hardwired path
> to dclerk.  There is no
> other way to interpret that if he was speaking
> literally, which I assume he
> was.
> 
> It's not as portable or versatile as it could be. 
> That's all I meant.
> 
> mark->

Mark, you are correct, and so is Mr. Cole of course. 
Normally I do not hard code the path to the fp
programs for the reasons that you mentioned.  In this
case however I was going to hard-code them anyway
because they are that way already and I want to be
consistent.

I could go back and change all of the existing
references, and perhaps some day I will do that, but
that is not what the client is paying me for right
now.

Thanks for the suggestion.  It was certainly a good
observation.

Jeff Harrison
jeffaharrison at yahoo.com

Author of JHExport and JHImport.  The easiest and
fastest ways to generate code for filePro exports and imports.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com