From: Christoph Reller <christoph.reller@gmail.com>
To: ntg-context <ntg-context@ntg.nl>
Subject: Input file name containing full stop "."
Date: Wed, 9 Sep 2020 10:56:09 +0200 [thread overview]
Message-ID: <CAO8LnPG=u2A6uBO-=VS4hm28Vwqsx5JUCOEJjEUEVydMdXAiYQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 652 bytes --]
Dear list,
I am using ConTeXt LMTX Version 2020.09.05 21:18 with an input file named,
e.g., "test.test.tex". When compiling, ConTeXt generates files "test.log",
"test.tua", "test.pdf".
ConTeXt MKIV used to produce files "test.test.log", "test.test.tua",
"test.test.pdf".
Is there a way for ConTeXt LMTX to process input files that contain full
stops consistently? I am aware of the "--result=..." option, but what about
the "...tua", "...log" and synctex files? This is a serious problem when
running multiple compilations in parallel, e.g., on "test.a.tex" and
"test.b.tex", because both processes use the same "test.tua" file.
Cheers,
Christoph
[-- Attachment #1.2: Type: text/html, Size: 925 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2020-09-09 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 8:56 Christoph Reller [this message]
2020-09-09 11:20 ` Marco Patzer
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='CAO8LnPG=u2A6uBO-=VS4hm28Vwqsx5JUCOEJjEUEVydMdXAiYQ@mail.gmail.com' \
--to=christoph.reller@gmail.com \
--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).