Per Jessen <[EMAIL PROTECTED]> wrote: >> it helps, think of the CONFIGFILE directive as a URL that Analog >> uses to read in additional text. Entering a URL for www.analog.cx >> doesn't transport you or your computer to Christmas Island, and the >> CONFIGFILE > > Uh, but it does - somewhat. Once you specify eg. www.analog.cx as the > host/site name each and every subsequent reference is relative to > that. When you burrow further down the directory tree, still each > reference remain relative to the directory you're currently in. To > reference the directory you started out in, you need to make an > absolute reference.
But it doesn't - the browser converts each of those "relative URLS" into explicit URLs before requesting them. If you want to include the same image in pages on many different websites, you have to use an explicit URL, just as, if you want to include the same configfile in many different analog setups, you should use explicit paths to avoid any confusion about where things will end up. > I find it > counter-intuitive at the moment - whenever I use CONFIGFILE I need to > remember where this particular config-file may or may not have been > imbedded/included from. ?? I find it's exactly the opposite - with the way Analog works now, I don't have to worry about where I include files from, because I know exactly where the "current working directory" is, and I don't have to worry about files being splattered all over the place because the context was changed when I included a file. Aengus +------------------------------------------------------------------------ | This is the analog-help mailing list. To unsubscribe from this | mailing list, go to | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | List archives are available at | http://www.mail-archive.com/analog-help@;lists.isite.net/ | http://lists.isite.net/listgate/analog-help/archives/ | http://www.tallylist.com/archives/index.cfm/mlist.7 +------------------------------------------------------------------------
