From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: --silent and so on
Date: Wed, 22 Jul 2020 18:08:05 +0200 [thread overview]
Message-ID: <ecfbfdb3-87b2-9585-b58f-d635360667a1@gmail.com> (raw)
In-Reply-To: <78766f27-874e-83d0-8446-7eba4c324b20@free.fr>
thierry horsin schrieb am 22.07.2020 um 17:57:
> Hi everybody
>
> I am a current context user since now many years and in particular I use
> it on linux with automatic compilation with a bash script detecting any
> modifications of the .tex file. In order for this to work I used with
> previous versions
>
> the "--nonstopmode --batchmode --silent --noconsole" compilation options.
>
> With these options with a new error in the .tex files with old versions
> of mkiv the previous pdf produced was not changed. Now with lmtx,
> appears a single page pdf file with ERROR written on it. Are there
> compulations options with lmtx in order to have something similar as
> before ?
context --nodummy <file>
Wolfgang
___________________________________________________________________________________
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 prev parent reply other threads:[~2020-07-22 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 15:57 thierry horsin
2020-07-22 16:08 ` Wolfgang Schuster [this message]
2020-07-22 16:12 ` thierry horsin
2020-07-23 12:39 ` Taco Hoekwater
2020-07-23 14:21 ` Hans Hagen
2020-07-23 14:25 ` Taco Hoekwater
-- strict thread matches above, loose matches on Subject: below --
2020-05-04 11:35 Thierry Horsin
2020-05-04 13:19 ` Taco Hoekwater
2020-05-04 16:20 ` 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=ecfbfdb3-87b2-9585-b58f-d635360667a1@gmail.com \
--to=wolfgang.schuster.lists@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).