This is the mail archive of the
mailing list for the Cygwin project.
- From: Nicholas Wourms <nwourms at yahoo dot com>
- To: Olaf Weber <olaf at infovore dot xs4all dot nl>, Thomas Esser <te at dbs dot uni-hannover dot de>
- Cc: rodmedina at cantv dot net, cygwin at cygwin dot com
- Date: Sun, 15 Sep 2002 15:18:06 -0700 (PDT)
- Subject: Re: none
--- Olaf Weber <firstname.lastname@example.org> wrote:
> Thomas Esser writes:
> >> 3-All the fonts are allways done in the working directory and
> >> in VARTEXFONTS. The problem is due to the kpathsea script
> mktex.opt. Here
> >> the path-separator is set SEP=';' as in DOS, but CYGWIN is like
> >> The problem is that such script uses the fact that COMSPEC is
> >> to deduce that the OS is DOS-WINDOWS. In CYGWIN COMSPEC is also
> > Well, kpsewhich knows the separator it was compiled with. So, the
> > fix to this problem would be to add an option to kpsewhich that
> > it output this character and then use this for setting $SEP.
> > [-> Olaf, WDYT?]
> Hm. Urgh. I suppose that could work.
> What's Cygwin's equivalent of DOS drive letters? Does C:\foo
> translate to //c/foo, so that there will be no colons in paths?
> I do not use cycwin myself, but do need/want some information about
> this kind of thing before applying cygwin-specific patches. In
> particular, this may help the cygwin-relevant bits survive any
> rewrites of code.
What's the word on Omega? They still holding out on you guys?
Do you Yahoo!?
Yahoo! News - Today's headlines
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html