From: Marco Patzer via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Marco Patzer <lists@homerow.info>
Subject: Re: Few quick questions
Date: Tue, 8 Mar 2022 21:26:39 +0100 [thread overview]
Message-ID: <20220308212639.7ead1416@homerow> (raw)
In-Reply-To: <47b198f885e97699b0e71b5e72e6705211d320de.camel@out-world.com>
On Tue, 08 Mar 2022 20:45:17 +0100
Christoph Hintermüller via ntg-context <ntg-context@ntg.nl> wrote:
> Hans indicated a tool, a program, which allows to verify that that
> all start* stop* tag pairs are symmetric and placed in correct
> order. I just cant remember how it is called. Can anybody help
> here?
mtxrun --autogenerate --script check <file>
The following will not report missing tags but will find other
common issues and report them on the console:
context --errors='*' <file>
Marco
___________________________________________________________________________________
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:[~2022-03-08 20:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 19:45 Christoph Hintermüller via ntg-context
2022-03-08 20:26 ` Marco Patzer via ntg-context [this message]
2022-03-09 10:21 ` Christoph Hintermüller via ntg-context
2022-03-09 16:26 ` Christoph Hintermüller via ntg-context
2022-03-09 16:36 ` Hans Hagen via ntg-context
2022-03-08 19:54 Christoph Hintermüller via ntg-context
2022-03-08 20:00 ` Rik Kabel via ntg-context
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=20220308212639.7ead1416@homerow \
--to=ntg-context@ntg.nl \
--cc=lists@homerow.info \
/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).