ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan BRASLAU <alan.braslau@cea.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: nomarking function in MKIV
Date: Thu, 1 Jul 2010 20:59:27 +0200	[thread overview]
Message-ID: <201007012059.27547.alan.braslau@cea.fr> (raw)
In-Reply-To: <E62F48E7-6B56-4E01-AA28-F1865E44BB2E@uni-bonn.de>

On Thursday 01 July 2010 12:00:45 Thomas A. Schmitz wrote:
> On Jul 1, 2010, at 11:44 AM, Alan BRASLAU wrote:
> > No one has answered my question about to what belongs any text
> > between a proceding \stopchapter and a following \startchapter, as in
> > \startchapter{title}
> > \stopchapter
> > some text
> > \startchapter{next title}
> > \stopchapter
> 
> Excuse me, but your question is just plain nonsense. What you show us is
> sloppy writing. Why should ConTeXt or any other system cater to this?
> You're asking "where does text belong that doesn't belong to any
> hierarchical structure of my document?" The answer is obvious: this text
> doesn't belong anywhere.

This is a very good answer.

Now, think about robustness. So called sloppy writing
can easily happen in a very big project, or more likely
by an inexperienced user. ConTeXt is pretty good in handling
this, but not perfect. How many times have we tried options
that do not exist and which are simply ignored in silence.

Now try:
  \input knuth
  \starttext
  What about this?
  \stoptext

Sometimes our errors, ignored in silence, end up having
strange side effects that are long to debug. I came across
this, for example, using by mistake \cite{reference}
rather then \cite[reference].

Back to robustness, I once wrote a very big system used to run
expriments. It *had* to be robust. Luckly, to insure this,
I had a collegue who was very good in doing every thing wrong.
For example, if the program asked "how many cycles" to run,
he was capable of typing "yes". Why not?
The program still had to handle this correctly.
Should be the same for typesetting.

I hope that you all *never* make mistakes.
Remember, *real* unix users only use cat;
All other text editors are for "sissys".

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
___________________________________________________________________________________


  parent reply	other threads:[~2010-07-01 18:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29 16:14 John Devereux
2010-06-29 17:33 ` Peter Münster
2010-06-29 21:03   ` John Devereux
2010-06-30  8:19   ` Alan BRASLAU
2010-06-30  9:03     ` Peter Münster
2010-06-30 10:03       ` nomarking function in MKIV (selector) Alan BRASLAU
2010-06-30 22:35     ` nomarking function in MKIV Wolfgang Schuster
2010-07-01  8:16       ` Alan BRASLAU
2010-07-01  8:30         ` Wolfgang Schuster
2010-07-01  9:23         ` Peter Münster
2010-07-01  9:44           ` Alan BRASLAU
2010-07-01  9:55             ` luigi scarso
2010-07-01 10:00             ` Thomas A. Schmitz
2010-07-01 10:23               ` luigi scarso
2010-07-01 18:59               ` Alan BRASLAU [this message]
2010-07-02  8:18                 ` Thomas A. Schmitz
2010-07-02  9:18                   ` luigi scarso
2010-07-02 11:07                   ` Alan BRASLAU
2010-07-01 10:11             ` Henning Hraban Ramm

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=201007012059.27547.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).