Home > Archive > Tcl > November 2006 > Problem installing cgi.tcl on winXP
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Problem installing cgi.tcl on winXP
|
|
| Merrilee Larson 2006-11-25, 7:02 pm |
| Hi...
Problem with the "mail" functionality in cgi.lib. I guess I have one of two
choices: 1) use a "sendmail" replacement 2) setup "cgi_mail_relay". The
latter needs $host to contain something. Where do I set *that* up? IMHO, there
should be a set of global variables at the beginning of the script to adapt
this library to be site-specific.
If I choose option #1, how would I write the winXP path to the executable --
i.e., single/double forward slashes or single/double back slashes. TIA..
--
duke
| |
| Aric Bills 2006-11-25, 7:02 pm |
|
Merrilee Larson wrote:
> Hi...
>
> Problem with the "mail" functionality in cgi.lib. I guess I have one of two
> choices: 1) use a "sendmail" replacement 2) setup "cgi_mail_relay". The
> latter needs $host to contain something. Where do I set *that* up? IMHO, there
> should be a set of global variables at the beginning of the script to adapt
> this library to be site-specific.
>
> If I choose option #1, how would I write the winXP path to the executable --
> i.e., single/double forward slashes or single/double back slashes. TIA..
> --
> duke
Can't help you with the cgi stuff, but if you go with option #1, you
can write your path with single forward slashes:
exec c:/my/program.exe arg1 arg2 arg3
Alternatively, you can also use double backslashes.
If you need to do anything fancy with file names/paths, you'll want to
look at the [file] man page. You may be especially interested in the
subcommands [nativename] and [normalize]. (If you're up for some
additional reading, other file subcommands I find extremely useful are
[tail], [rootname], [extension], [split], and [join].)
| |
|
| I experienced the same some time ago and I think I finally decided not
to wrap cgi sentences under the cgi_eval command...
I think that is all that was needed in my case...
jima
Aric Bills wrote:
> Merrilee Larson wrote:
>
> Can't help you with the cgi stuff, but if you go with option #1, you
> can write your path with single forward slashes:
>
> exec c:/my/program.exe arg1 arg2 arg3
>
> Alternatively, you can also use double backslashes.
>
> If you need to do anything fancy with file names/paths, you'll want to
> look at the [file] man page. You may be especially interested in the
> subcommands [nativename] and [normalize]. (If you're up for some
> additional reading, other file subcommands I find extremely useful are
> [tail], [rootname], [extension], [split], and [join].)
|
|
|
|
|