Glenn McCorkle wrote:
>
> BTW, Those .DGIs might help users to understand how a .DGI works.
> As you can see, .DGIs are not much more than batch files.
> The only difference being that each command is not on it's own line.
> They are seperated by "\n" and placed all on one line.
> (and we must use "\\" not "\" for path indicators)<g>
Glenn, those are very useful examples but as examples they fail to address
the area of .DGIs that I personally find confusing.
I find it easy to understand WHAT happens on the RIGHT side of the "|".
It's mime.cfg and the left side that leaves me uninformed. <G>
For example:
> application/x-arachne-package APM>HTM|@md \\backup \n md \\backup\\arachne \n
> pkzip -ex \\backup\\arachne\\ara-back.zip \\arachne\\*.cfg \n
> $eapm.exe -u $u $1>$2
>
> file/.apm >HTM|@md \\backup \n md \\backup\\arachne \n
> pkzip -ex \\backup\\arachne\\ara-back.zip \\arachne\\*.cfg \n
> $eapm.exe -u $u $1>$2
>
> (remember, these lines have been broken for eMail)
Why are BOTH of these required ?
- They seem to be identical on the right side.
Why is there an ">HTM" on the left side of the "|"
- The result is a .zip and the commands and input are text.
If the example is correct, how did you know the answers to those questions ?
And finally, what happens if the directory(s) already exist(s) ?
Maybe it is time once again to consider talking about the secrets of mime.cfg.
<G>
- Clarence Verge
--
- Help stamp out FATWARE. As a start visit: http://home.arachne.cz/
--
