ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Adaptive section structuring
Date: Thu, 13 Sep 2012 11:29:06 +0200	[thread overview]
Message-ID: <FF2F4517-F48D-4243-B468-CB31D7F19298@gmail.com> (raw)
In-Reply-To: <20120913110714.559d6728@homerow>


Am 13.09.2012 um 11:07 schrieb Marco Patzer <homerow@lavabit.com>:

>>> Is there something like an adaptive structure code which keeps track
>>> of the nesting level? In this example the first structure would
>>> become the chapter, the second one a section, etc.
> 
>> \startstructurelevel [title=first lower level]
>>     \startstructurelevel [title=second lower level]
>>         \startstructurelevel [title=third lower level]
>>             test
>>         \stopstructurelevel
>>     \stopstructurelevel
>> \stopstructurelevel
> 
> Brilliant. That's it. Thanks also to Wolfgang.
> 
> Is there a preferred syntax to use either sectionlevel or
> structurelevel?

I would go with \startsectionlevel which is the new name for the command but
the old name \startstructurelevel can be also used.

Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________


      reply	other threads:[~2012-09-13  9:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13  7:48 Marco Patzer
2012-09-13  8:00 ` Wolfgang Schuster
2012-09-13  8:10 ` Hans Hagen
2012-09-13  9:07   ` Marco Patzer
2012-09-13  9:29     ` Wolfgang Schuster [this message]

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=FF2F4517-F48D-4243-B468-CB31D7F19298@gmail.com \
    --to=wolfgang.schuster@gmail.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).