From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
"Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: Are nested sections possible?
Date: Thu, 24 Mar 2016 22:11:53 +0100 [thread overview]
Message-ID: <56F45819.3040705@wxs.nl> (raw)
In-Reply-To: <20160315130927.2b9a0cbe@cea.fr>
On 3/15/2016 8:09 PM, Alan BRASLAU wrote:
> On Tue, 15 Mar 2016 18:10:27 +0100
> "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de> wrote:
>
>> But don't let anyone
>> tell you that explicit names are "antiquated." They make TeX or xml
>> source documents so much more readable! And when you have to retrace
>> five levels of \startsectionlevels because you want to change the
>> structure of your document, you will rue the day you abandoned proper
>> names.
>
> When you want to change the structure of your document when using
> structure levels, all that you need do is add or subtract a level of
> nesting. With named levels, it is easy to create complicated documents
> that jump around in level, which would be pretty messy.
on the other hand, when you look at a piece of coded document you no
longer know if you're in an important chapter or unimportant
subsubsubsubsubsubsection
so, in the end it all boils down to circumstances and usage which is why
we have several methods
> What a nightmare it would be to add or subtract a named structure level
> in a complicated document.
>
> This being said, I still mostly use named structure levels myself, as
> old habits are hard to change (but don't tell Hans this!).
ha, well, if i remember right this nested anonymous sectioning was added
on your request .. so it is now one of those orphaned features
anyway, i tend to replace
\chapter{foo}
by
\startchapter[title=foo]
\stopchapter
but at a much lower level keep using \subsubsection and alike
(also because then with chapters one can more conveniently set other
properties)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2016-03-24 21:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 8:08 mica
2016-03-11 8:23 ` josephcanedo
2016-03-11 8:36 ` Pablo Rodriguez
2016-03-11 8:43 ` Mica Semrick
2016-03-12 0:53 ` Alan BRASLAU
2016-03-14 8:05 ` Procházka Lukáš Ing.
2016-03-15 16:54 ` Alan BRASLAU
2016-03-15 17:10 ` Thomas A. Schmitz
2016-03-15 19:09 ` Alan BRASLAU
2016-03-24 21:11 ` Hans Hagen [this message]
2016-03-24 21:08 ` Hans Hagen
2016-03-14 8:52 ` Pablo Rodriguez
2016-05-20 4:39 ` docent.einstein
2016-03-11 9:37 ` Andreas Schneider
2016-03-11 9:43 ` Hans Hagen
2016-03-11 15:42 ` Mica Semrick
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=56F45819.3040705@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=thomas.schmitz@uni-bonn.de \
/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).