ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Lukáš Procházka" <LPr@pontex.cz>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Redirect compilation to another .pdf?
Date: Sun, 10 Apr 2016 12:39:19 +0200	[thread overview]
Message-ID: <op.yfo87tsmf14xzu@lkzd-2013> (raw)
In-Reply-To: <57097BF0.3060107@gmx.es>

Hello,

thanks for the tip,

the issue here is that I'm not using AR but PdfXChange Viewer (and yes, there is also at least SumetraPPDF and Foxit Reader).

I don't use --autopdf as it closes the .pdf as soon as the compilation is to start.

My way is to compile into a "shadow copy" which allow use to view the document even during its compilation.
Once the compilation is done, I close the .pdf, I move the compiled "shadow copy" to the well-named .pdf and I open it in a viewer.

So I'm trying find a way to redirect ConTeXt to that "shadow copy"...

Best regards,

Lukas (and yes, WinXP)


On Sun, 10 Apr 2016 00:02:24 +0200, Pablo Rodriguez <oinos@gmx.es> wrote:

> On 04/09/2016 11:47 PM, Pablo Rodriguez wrote:
>> On 04/09/2016 10:11 PM, Lukáš Procházka wrote:
>>> Hello,
>>>
>>> is there a way to tell ConTeXt to generate a .pdf named othe
>>> instead of the name derived from file to be compiled?
>> [...]
>> BTW, ---auto may achieve what you intend. I have never used it.
>
> Sorry, the option is --autopdf, not --auto.
>
> Pablo


-- 
Ing. Lukáš Procházka | mailto:LPr@pontex.cz
Pontex s. r. o.      | mailto:pontex@pontex.cz | http://www.pontex.cz
Bezová 1658
147 14 Praha 4

Tel: +420 241 096 751
Fax: +420 244 461 038

___________________________________________________________________________________
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:[~2016-04-10 10:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-09 20:11 Lukáš Procházka
2016-04-09 20:51 ` Alan BRASLAU
2016-04-09 21:37   ` Pablo Rodriguez
2016-04-09 22:02     ` Jan Tosovsky
2016-04-09 21:47 ` Pablo Rodriguez
2016-04-09 22:02   ` Pablo Rodriguez
2016-04-10 10:39     ` Lukáš Procházka [this message]
2016-04-10 16:07       ` Aditya Mahajan
2016-04-10 16:22         ` Hans Hagen
2016-04-10 19:49         ` Lukáš Procházka
2016-04-10 21:43           ` Hans Hagen
2016-04-11  7:23             ` Procházka Lukáš Ing.
2016-06-06  7:21             ` Procházka Lukáš Ing.
2016-06-06  7:44               ` Hans Hagen
2016-04-10 13:09   ` 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=op.yfo87tsmf14xzu@lkzd-2013 \
    --to=lpr@pontex.cz \
    --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).