ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Keith J. Schultz" <keithjschultz@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Overriding pdfview
Date: Fri, 28 Jun 2013 15:16:37 +0200	[thread overview]
Message-ID: <A5CB7ED0-1783-4CA3-9E65-E2B9FC1387E4@web.de> (raw)
In-Reply-To: <51CD66CE.1060101@wxs.nl>

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 <pragma@wxs.nl>:

> 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]
___________________________________________________________________________________
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-28 13:16 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=A5CB7ED0-1783-4CA3-9E65-E2B9FC1387E4@web.de \
    --to=keithjschultz@web.de \
    --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).