At 02:44 PM 2/6/2003 -0500, Guo Yang wrote:
Hans
Your suggestion sovled my problem too. Thank you very much!
I don't know if anybody mentioned it here or not, I did have a couple issues using texexec.pl and texutil.pl under cygwin enviroment. For the texexec.pl case, it turned out that it caused by the different naming scheme for the path, i.e., '\' and '/'. So I added a conditional test in the RunPerlScript subrouting in texexec.pl to make it work in both cmd and cygwin. For texutil, I found that somehow it writes a '^M' in the middle of a comment line and leaves strange number in the list of contents page. So I commented these two lines out in texutil.tex and 'sovled' the problem:
sub FlushFiles {print TUO "%\n" . "% $Program / Files\n" . "%\n" ; # foreach $FILE (keys %Files) # { print TUO "% $File ($File{$File})\n" }
I am wondering these problem, if they are, can be corrected in the future release. Or if they are not, how to solve them without chaning the programs. I understand that most of people using integrated enviroment. But I believe there are still some people like using command line :))
I don't understand this since it's just a message you comment. What is the error message? maybe fabrice (windows path expert) know what is goidn on Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------