Re: texdoc --view termination behavior

I'm calling texdoc from a cross-platform application. Therefore, the 
call should be as system- and program-agnostic as possible (working with 
MikTeX and Texlive on any OS).

Even disregarding this, modifying env is not ideal in either way:

a) Removing MIKTEX_VIEW_* would modify user settings and therefore is 
not an option.
b) When adding MIKTEX_VIEW_* I would have to find out proper viewers on 
the users system. This is not someting I want to care about.

Nether is a viable solution. Therefore, I currently have to workaround 
the different behaviors of texdoc in MikTeX. This is includes a) 
detecting which texdoc is actually used (MikTeX or Texlive) and if 
MikTeX b) adapt the program logic to expect texdoc to return or not 
depending if MIKTEX_VIEW_* is set or not. It's all possible, but it's 
quite cumbersome.

-----Original Message-----
From: Tim Hoffmann [mailto:[email protected]]
Sent: Sunday, May 17, 2015 2:14 PM
To: [email protected]
Subject: [MiKTeX] texdoc --view termination behavior

texdoc --view behaves differently depending on if the MIKTEX_VIEW_*|environment variable is set.

If not set, texdoc calls the appropriate viewer and exits.
If set, the texdoc process stays open until the viewer is closed.

This behavior different behavior is quite inconvenient, when controlling and checking the call from another program. Is it possible to make texdoc start a detached process for the viewer and immediately exit even if the MIKTEX_VIEW_* variables are set?

Thanks,
Tim



------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y