On 6/26/2013 11:27 PM, Bill Meahan wrote:
That was my original question: how do I change the default without hand-editing a file in the base distribution? That's not only bad practice, it's liable to get overwritten on the "next" update.
as mentioned in an earlier mail ... you can set it in a user properties file and the last settings loaded are taken (which happen to be user properties)
Does one use texmf.cnf or something else with a very recent MKIV?
Although I first discovered this when trying to use SciTE, it does the same thing if invoked from the command line. The pdf viewer does not appear in any of the SciTE *.properties files.
I haven't settled on SciTE as the editor I want to use but a SciTE-only workaround misses the point.
in any editor, when one wants to run context, mtxrun --script context has to be configured and adding --autopdf=acrobat is then no big deal
maybe context --autopdf=acrobat
context --autopdf=fullacrobat When run from the cmd.exe command line, acrobat _does_ get launched _but_ it gets launched before ConTeXt has created the pdf file then hangs so the only way to exit is a Ctrl-C in the cmd.exe window. Simply closing acrobat simply causes acrobat to launch again.
it has to do with the fact that only files opened with pdfopen.exe can be closed with pdfclose.exe .. both programs already have to jump through loops to get that done
A better solution would be to assume the person installing ConTeXt does not have a PDF reader *at all* and include some minimal self-contained reader (no dll's needed) in the distribution itself, the way rsync is included. I really don't care which one, as long as there is *something* present. MuPDF might be a good choice but I'm quite sure everyone on the list has a favorite they would like to see as the "included" viewer for one reason or another. As long as ConTeXt is guaranteed to find it, it is a good default.
i suppose that summatrapdf can be put in the texmf-mswin/bin path .. after all. the portable version is not depending on other components btw, is nothing is present, context will still run ok with --autopdf ... okay one will need a printer then as said: acrobat just became too inconvenient for me to use in a fast edit/view cycle (pop ups, dialogs, conflicts between professional and reader, etc. makes me wonder where it's heading); i still use professional for proofing, inspection and presentations (when some javascript related features and/or layers and/or structure is needed). Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------