From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Redirect compilation to another .pdf?
Date: Sun, 10 Apr 2016 18:22:40 +0200 [thread overview]
Message-ID: <570A7DD0.7020403@wxs.nl> (raw)
In-Reply-To: <alpine.OSX.2.02.1604101202300.3098@nqv-znpobbx>
On 4/10/2016 6:07 PM, Aditya Mahajan wrote:
> On Sun, 10 Apr 2016, Lukáš Procházka wrote:
>
>> 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"...
>
> This should have worked, but for some reason it does not:
>
> context --jobname=shadow main.tex
>
> The output says:
>
> system > files > jobname 'shadow', input './main', result 'shadow'
> .....
> mkiv lua stats > result saved in file: shadow.pdf, compresslevel 3,
> objectcompresslevel 3
>
> but no shadow.pdf file is created.
because we do all kind of analysis command line arguments and given
filenames and then set variables reflecting paths, input filenames, file
types ... (we could probably do some magic with a specific pdf
outputfile but i don't like that idea as it's a workaround for a problem
that should not be there in the first place .. waste of time and energy)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | 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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-04-10 16:22 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
2016-04-10 16:07 ` Aditya Mahajan
2016-04-10 16:22 ` Hans Hagen [this message]
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=570A7DD0.7020403@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).