A fairly usable variable substitution syntax would be:

${name} references a name being an internal one (the options)
                or an external one (ENV).

Maybe it is a consideration to allow references to other
options.., then you don't need a += like syntax but more something like:

option1 = "World"
option2 = "Hello, ${option1}!"
;)

Then please also consider an option name for the url
on the commandline.

Another one:
        I lately had to post on a web server and it would be nice if I
        could 've said:
                curl -K config --arguments <info1> <info2>
        where the config file specified:
                ....
                -F "item1=${arg0}" -F "item2=${arg1}"
                ....
        as this would hide some "internals" of the form
        from a user. (less prone to errors, without adding an
        extra layer of scripting ;-).
        it would also allow "constructing" a reference url
        where the base is in a config file, and the remaning parts
        are "outside".

just my 0.02

regards,
Nico Baggus

-----------------------------------------------------------------
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.

Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-----------------------------------------------------------------
Received on 2000-11-02