From: Alan BRASLAU <alan.braslau@cea.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: structure sanity checks
Date: Wed, 13 Oct 2010 14:29:47 +0200 [thread overview]
Message-ID: <201010131429.47796.alan.braslau@cea.fr> (raw)
Using \startchapter\stopchapter or \startitem\stopitem could present
some logical advantage over the use of \chapter or \item, for example.
However, it would be useful to have some sort of sanity check
giving warnings at least if the \start\stop symmetry is violated.
As a minimal example, the following simple case of one logical error
leads to an undesired result. Of course, you get what you asked,
but some sort of warning could be useful. Or, rather, is the general
philosophy to silently pass over such errors so as not to load down
the log in the face of such user errors?
Indeed, under ConTeXt, unknown or incorrect arguments are simply ignored.
(in other cases, for example forgetting \stoptext, ConTeXt protests vocally)
Alan
\starttext
\startitemize [n]
\startitem
first
\startitem
\startitem
second
\stopitem
\stopitemize
\stoptext
___________________________________________________________________________________
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:[~2010-10-13 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 12:29 Alan BRASLAU [this message]
2010-10-13 12:39 ` luigi scarso
2010-10-14 13:57 ` 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=201010131429.47796.alan.braslau@cea.fr \
--to=alan.braslau@cea.fr \
--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).