Hi Hans,
I meant a OS system variable. But that actually does not matter.
The default action would be changed to not call a browser!
I agree that nobody should be forced to use autopdf.
Yet, as I understand the discussion there seems to be a need
to add some generality to the method.
Possibly, a cleaner way to resolve this discussion is to define calls for
user as in user defined. In other words, in addition to -autopdf there will be
a parameter -autocalls which is a list of commands for the calls opencalls, closecalls,
allcalls.
No for more need for anyone to really change a file it would be in their call to context.
regards
Keith.
Am 28.06.2013 um 12:34 schrieb Hans Hagen
On 6/28/2013 10:56 AM, Keith J. Schultz wrote:
Hi All,
I would agree that the users default should be respected.
I will have to contradict my last post them.
My suggestion them is to use a system variable such as ConTeXtViewer. This variable would contain the program to be called. If it is not set or empty context simply finishes up what ever it is doing and exits.
in that case it would be a directive in texmfcnf.lua (probably in the texmflocal instance) but when unset there still will be the default
no one is forced to use --autopdf and if someone doesn't want to pop up a browser one can simply nto use --autopdf
keep in mind that when a user uses --autopdf he/she probably knows what is needed can can as well pass some extra info [snip, snip]