Dennis Ruffer wrote: > > Oh, that problem again. Yet another brain fart. Sorry! ;) > > I am running the latest (1.3.20-1), so unless you are saying that you are > going to drop cygwin entirely, a compromise is needed here.
Ok, I have now made some postings on the cygwin mailing list, and received some enlightening comments, in particular <http://cygwin.com/ml/cygwin/2003-03/msg00879.html> The story is, that, if we have "\" in the filename, a filename is a Windows filename. If it starts with "/", it is relative to the current drive, not relative to the Cygwin POSIX root "/". Since most Gforth users on Windows don't care for the POSIX root, and won't have more of cygwin than just the dll delivered with Gforth, it is a good idea to make "\" the default path separator. We probably have to set up the default paths for Windows installation differently, though (but since few people do that, we can probably leave it to them). You could do that, but since you actually want your Cygwin Gforth to behave as like a Unix Gforth, you probably should just configure it as Unix Forth (example shown below), and be happy. > > configure --build i686-linux This takes care of both, the path separator and the newline (and AFAIK of nothing else). Good compromise? - anton --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
