ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Overriding pdfview
Date: Thu, 27 Jun 2013 00:24:55 +0200	[thread overview]
Message-ID: <51CB6A37.9030509@wxs.nl> (raw)
In-Reply-To: <51CB5CC0.8090505@meahan.net>

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 <yourfile.tex>
>>> context --autopdf=fullacrobat <yourfile.tex>
>>
>
> 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
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2013-06-26 22:24 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-26 13:53 Bill Meahan
2013-06-26 14:20 ` luigi scarso
2013-06-26 15:17   ` Bill Meahan
2013-06-26 16:11     ` luigi scarso
2013-06-26 19:29       ` Hans Hagen
2013-06-26 20:22         ` luigi scarso
2013-06-26 20:36           ` Siep Kroonenberg
2013-06-26 21:09             ` luigi scarso
2013-06-26 20:50           ` Philipp Gesang
2013-06-26 20:58             ` Hans Hagen
2013-06-26 21:16               ` luigi scarso
2013-06-26 21:34               ` Philipp Gesang
2013-06-27 15:15             ` Sietse Brouwer
2013-06-27 15:44               ` Mica Semrick
2013-06-27 17:25               ` Aditya Mahajan
2013-06-27 19:39                 ` Arthur Reutenauer
2013-06-27 18:18               ` Hans Hagen
2013-06-26 21:27         ` Bill Meahan
2013-06-26 22:24           ` Hans Hagen [this message]
2013-06-26 23:02             ` Bill Meahan
2013-06-27  7:21               ` luigi scarso
2013-06-27  2:21         ` hwitloc
2013-06-27  7:35           ` luigi scarso
2013-06-27  8:13             ` Hans Hagen
     [not found] <mailman.1497.1372359752.2084.ntg-context@ntg.nl>
2013-06-27 19:43 ` Pavneet Arora
2013-06-27 22:44   ` luigi scarso
2013-06-27 23:46     ` Sietse Brouwer
2013-06-27 23:53       ` Gareth Jones
2013-06-28  8:56         ` Keith J. Schultz
2013-06-28 10:34           ` Hans Hagen
2013-06-28 13:16             ` Keith J. Schultz
2013-07-01  2:31           ` David Rogers
2013-06-28  8:28       ` Hans Hagen
2013-06-28  2:29     ` Arthur Reutenauer
2013-06-28  6:23       ` luigi scarso
2013-06-28  8:29 Keith J. Schultz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51CB6A37.9030509@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).