[tex-live] pretest: texdoc problem

Reinhard Kotucha reinhard.kotucha at web.de
Sun Jul 26 22:47:46 CEST 2009

On 26 July 2009 Uwe Siart wrote:

 > Uwe Siart <uwe.siart at tum.de> writes:
 > > Reinhard Kotucha <reinhard.kotucha at web.de> writes:
 > >
 > >> On 26 July 2009 Uwe Siart wrote:
 > >>
 > >>  > When I reported this bug I could not call texdoc at all. It was provoked
 > >>  > by my MSYS installation with a shell script named 'shell' on PATH. But
 > >>  > this is fixed now in TL. texdoc no longer stumbles across my MSYS but
 > >>  > uses start.exe as intended.
 > >>
 > >> Did you have the MSYS bin directory in Windows PATH?  This would be
 > >> quite unusual.
 > >
 > > Yes, I did (and do). IIRC the MSYS installer put it there.
 > I installed the newly released MSYS 1.0.11 and can confirm that the
 > installer does *not* modify PATH. So it must have been me. I'm very
 > greedy in making GNUtools available on windows computers ;-) But as I
 > said: I never meant any harm by this.
 > So the correct way to use MSYS is
 > - not to put its bin directory on PATH
 > - use the utilities that come with MSYS exclusively from within the MSYS
 >   bash
 > Right?

Yes, this is what I remember.  I had to extract the files somewhere
and invoke a batch wrapper which launched a shell script.  The script
asked me some questions (for instance, whether I have installed MinGW
already and where).  Finally I added a shortcut to the start menu.

I'm still wondering what went wrong with texdoc and the only
explanation is that the start shell script was in PATH on Windows.
However, it still doesn't explain why it worked with TL-2008.  And I
don't know what Akira changed, so I still don't know what caused the


Reinhard Kotucha			              Phone: +49-511-3373112
Marschnerstr. 25
D-30167 Hannover	                      mailto:reinhard.kotucha at web.de
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.

More information about the tex-live mailing list