"Keith J. Schultz"
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.
It would not be two hard for a user to set this variable. Everybody gets what they want. It is not intrusive. It survives updates. Only needs to be done once.
Now, if anybody wants to us the current method and furture versions he can or set up he wants.
Windows, Mac, and Linux and other Unix-like systems all have such a system variable already, in their respective graphical desktop software. There is absolutely no need, and hardly any purpose either, in creating another setting - in fact it would only create further confusion. The respective already-existing settings for each OS were already mentioned earlier in this thread; all that's required for ConTeXt is to read the system setting that already exists and use it. If the user's default turns out to be not set, ConTeXt could do any combination of [complain] [open the user's system preferences for editing] [use its own default PDF software] [whatever else Hans et al have up their collective sleeve]. This means ConTeXt needs a small-but-cumbersome list of all the places to look where the user may have set their preferred PDF viewer, but that's just the price of being cross-platform. Anyone working with PDF is running a graphical desktop, right? I can see that people may prefer to work in terminal emulators as a matter of comfort/utility/familiarity, but is there anyone using ConTeXt and (on Linux or other Unix-like system) not running X11? (I think it's almost perfectly safe to assume that no Windows ConTeXt users are running straight DOS without a GUI...) -- David