ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <bourbaki@bigfoot.com>
Cc: ntg-context@ntg.nl
Subject: Re[2]: A proposal for the sectioning commangs
Date: Fri, 21 Jun 2002 23:15:27 +0200	[thread overview]
Message-ID: <1341671433.20020621231527@bigfoot.com> (raw)
In-Reply-To: <200206211127.50412.john@wexfordpress.com>

Friday, June 21, 2002 John Culleton wrote:

JC> In my very humble opinion this is a big part of the problem with tools
JC> such as XML and its children. Using two tags where one will do is just
JC> excessive clutter, and ends up with lines like
JC> \stopsubusubsection \stopsubsection \stopsection \stopchapter
JC> .... which is all superfluous code and offers the chance for keying errors on 
JC> every tag.  The computer is smart enough to know that a \chapter head 
JC> terminates all previous subordinate levels. And the person reading the code 
JC> is smart enough too. I see no virtue in this proposal. 

I thought I pointed out some of the pluses ... do you have any
specific idea to counter to any of the pluses (apart from the
folding thingie which is just a bonus)?

JC> No matter how elegant the code looks, in fact it is just a means to an end, 
JC> and the end is a publication, and all those meaningless stop tabs won't
JC> afffect the final document in any case. 

Actually it does, in those cases when you want to do something at
the END of all section blocks of the same type (e.g. a local ToC)
--just put the appropriate code in the \stop<sectionblock> hook.
Other aspects of how my idea CAN affect the final result of the
document is provided in my original post.

-- 
Giuseppe "Oblomov" Bilotta


  reply	other threads:[~2002-06-21 21:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-21 13:46 Giuseppe Bilotta
2002-06-21 15:27 ` John Culleton
2002-06-21 21:15   ` Giuseppe Bilotta [this message]
2002-06-21 22:37     ` Duncan Hothersall
2002-06-22  2:24       ` John Culleton
2002-06-23 21:47     ` Re[2]: " Hans Hagen
2002-06-23 10:45   ` Hans Hagen
2002-06-21 16:01 ` A proposal for the sectioning commands--addendum John Culleton
2002-06-21 21:17   ` Re[2]: " Giuseppe Bilotta
2002-06-23 19:39   ` Hans Hagen
2002-06-23 21:42     ` Re[2]: " Giuseppe Bilotta
2002-06-24  8:40       ` Hans Hagen
2002-06-24  8:55         ` Re[3]: " Giuseppe Bilotta
2002-06-24 18:06           ` texedit (was: something else) Henning Hraban Ramm
2002-06-25 15:47             ` Hans Hagen
2002-06-26 18:43               ` Henning Hraban Ramm
2002-06-27 16:54                 ` Hans Hagen
2002-06-28 21:48                   ` Henning Hraban Ramm
2002-06-23 10:43 ` A proposal for the sectioning commangs 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=1341671433.20020621231527@bigfoot.com \
    --to=bourbaki@bigfoot.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).