[tex-live] Debugging TeXdoc on Windows (TeX Live 2013)

[Lars Madsen]

just as a reference

texdoc texdoc

opens

/<path>/texlive/2014/texmf-dist/doc/texdoc/texdoc.pdf

/Lars Madsen
Institut for Matematik / Department of Mathematics
Aarhus Universitet / Aarhus University
Mere info: http://au.dk/daleif@imf / More information: http://au.dk/en/daleif@imf


________________________________________
From: Zdenek Wagner [zdenek.wagner at gmail.com]
Sent: 03 October 2014 14:17
To: Lars Madsen
Cc: Philip Taylor; TeXLive Mailing List
Subject: Re: [tex-live] Debugging TeXdoc on Windows (TeX Live 2013)

2014-10-03 14:03 GMT+02:00 Lars Madsen <daleif at math.au.dk>:
> Does it actuially know where Adobe Reader is? Can Adobe Reader be started from the dos prompt?
>
> Has the Adobe Reader executable been renamed in recent versions?
>
It happened to me even on Linux a long time ago. The problem is that
texdoc communicates with AR via pdfopen and the interface have change
(maybe even in a new version of AR). The default did not work but I
had to add something to texmf.cnf (I was lucky that I was able to run
"texdoc texdoc" on another computer and thus find the manual).
>
> /Lars Madsen
> Institut for Matematik / Department of Mathematics
> Aarhus Universitet / Aarhus University
> Mere info: http://au.dk/daleif@imf / More information: http://au.dk/en/daleif@imf
>
>
> ________________________________________
> From: tex-live [tex-live-bounces at tug.org] on behalf of Philip Taylor [P.Taylor at Rhul.Ac.Uk]
> Sent: 03 October 2014 13:55
> To: TeXLive Mailing List
> Subject: [tex-live] Debugging TeXdoc on Windows (TeX Live 2013)
>
> My TeXdoc has stopped working; trying (for example)
>
>         TeXdoc Makeindex
>
> from the TeX Live 2013 command prompt results in nothing.
> Inserting the "-l" qualifier yields :
>
>  1 D:\TeX\Live\2013\texmf-dist\doc\support\makeindex\makeindex.pdf
>  2 D:\TeX\Live\2013\texmf-dist\doc\support\makeindex\ind.pdf
>  3 D:\TeX\Live\2013\texmf-dist\doc\man\man1\makeindex.man1.pdf
> Please enter the number of the file to view, anything else to skip:
>
> and entering
>
>         1
>
> just takes me back to the command prompt.  Adobe Acrobat remains
> resolutely unlaunched.  File type associations appear to be normal, and
> double-clicking on a .PDF file in an Explorer window will launch
> Adobe Acrobat in the normal way, as will (for example) entering the name
> of a PDF file in the current directory from the CMD prompt.
> How might I best go about tracking down what has gone wrong ?
>
> Philip Taylor
>
>



--
Zdeněk Wagner
http://hroch486.icpf.cas.cz/wagner/
http://icebearsoft.euweb.cz