From: Alan BRASLAU <alan.braslau@cea.fr>
To: Keith Schultz <keithjschultz@icloud.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Structure of titles in MkIV
Date: Wed, 15 Oct 2014 16:10:02 +0200 [thread overview]
Message-ID: <20141015161002.060d9eb5@iram-ha-003840.extra.cea.fr> (raw)
In-Reply-To: <FA048D2F-62ED-4568-A656-21163605EA76@icloud.com>
On Wed, 15 Oct 2014 14:25:11 +0200
Keith Schultz <keithjschultz@icloud.com> wrote:
> BUT, Michal I believe has a point. Or should I say has come across a
> FLAW, according to my view of things. ConTeXt should warn...
I was warned (a few years ago) on the mailing list NOT to place any
text outside of structure elements. For example,
\starttext
This is a forward.
\startchapter[title=First chapter]
\input tufte
\stopchapter
This is a an afterthought.
\stoptext
Of course, this works, but I was warned that everything might not work
correctly as expected outside of the structure, since such text is
"nowhere".
I cannot remember the example of what had gone haywire, but I leaned my
lesson (and started systematically using \start\stop for everything,
well, not for paragraphs as I find that a bit too heavy...).
As to WARNINGS: ConTeXt generally silently ignores incorrect coding,
unknown options, etc. One might call for all sorts of "bells and
whistles" but these come at a performance cost so I have also learned
to do without them. Of course, this sometimes makes debugging one's
errors a bit more difficult, but after 10 years or so of practice one
will no longer make many errors! (one of my favorites still is
"\startext") ;-)
Alan
___________________________________________________________________________________
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 prev parent reply other threads:[~2014-10-15 14:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 11:49 Michał Goliński
2014-10-15 7:42 ` Alan BRASLAU
2014-10-15 7:45 ` Alan BRASLAU
2014-10-15 12:25 ` Keith Schultz
2014-10-15 14:10 ` Alan BRASLAU [this message]
2014-10-16 9:32 ` Keith J. Schultz
2014-10-16 11:25 ` Hans Hagen
2014-10-16 13:34 ` Keith Schultz
2014-10-17 9:13 ` Alan BRASLAU
2014-10-18 11:57 ` Michał Goliński
2014-10-19 15:03 ` Alan BRASLAU
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=20141015161002.060d9eb5@iram-ha-003840.extra.cea.fr \
--to=alan.braslau@cea.fr \
--cc=keithjschultz@icloud.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).