From: "Lukáš Procházka" <LPr@pontex.cz>
To: ConTeXt <ntg-context@ntg.nl>
Subject: Redirect compilation to another .pdf?
Date: Sat, 09 Apr 2016 22:11:29 +0200 [thread overview]
Message-ID: <op.yfn41fpyf14xzu@lkzd-2013> (raw)
Hello,
is there a way to tell ConTeXt to generate a .pdf named otherwise instead of the name derived from file to be compiled?
Let's have A.tex to be compiled and an existing A.pdf which cannot be written into, e.g. due to being open by a viewer.
The "context.exe A.tex" fails as the A.pdf cannot be open for writing.
The "context.exe A.tex --result=A2.pdf" fails too, as Ctx tries to write into A.pdf (derived from A.tex) first and later tries to rename A.pdf to A2.pdf.
There is a way - "copy /y A.tex A2.tex & context.exe A2.tex" but it has some disadvantages - the .log, .tuc etc. will be named A2.log, A2.tuc etc., messages will refer to "A2" rather than to "A" etc.
So best seems to me to have an option to tell ConTeXt to produce a .PDF WITH A DESIRED NAME from the beginning... Is there a way to do so?
Best regards,
Lukas
--
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
___________________________________________________________________________________
next reply other threads:[~2016-04-09 20:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-09 20:11 Lukáš Procházka [this message]
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
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.yfn41fpyf14xzu@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).