From: context@vivaldi.net
To: ConTeXt <ntg-context@ntg.nl>
Subject: Check for parity of pair tags on source file to be closed
Date: Thu, 09 Jan 2020 13:00:23 +0100 [thread overview]
Message-ID: <83e080142ac64252ac7add7c81cebd02@vivaldi.net> (raw)
Hello,
in most cases, when a source file is to be closed, pair elements (tags)
should balanced.
This concerns e.g. { - }, \bgroup - \egroup, \startitemize -
\stopitemize, \if - \fi etc.
When we have a complicated project structure and when compiling the
topmost (root) source, a log for a disbalanced tag may appear, but the
unbalanced tag however may be difficult to find.
Is there a way to enable "watching" pair tags (at least mentioned
before) in the way that their disbalance would be reported (logged)?
Maybe a "enable tracker" could provide that...
Sample:
---- A.mkiv
\starttext
A
\input B.mkiv
\stoptext
---- B.mkiv
\startitemize
\item B
---- <- "\startitemize" is unbalanced (unfinished by \stopitemize) in
the scope of B.mkiv,
so a message/log ("unfinished \startitemize") should be printed
when B.mkiv is to be closed.
Best regards,
Lukas
___________________________________________________________________________________
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-01-09 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 12:00 context [this message]
2020-01-09 12:08 ` Pablo Rodriguez
2020-01-10 12:46 ` context
2020-01-10 20:32 ` Pablo Rodriguez
2020-01-11 21:47 ` Wolfgang Schuster
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=83e080142ac64252ac7add7c81cebd02@vivaldi.net \
--to=context@vivaldi.net \
--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).