ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Setting table of contents depth by number rather than by list
Date: Sat, 25 Dec 2021 01:00:26 +0100	[thread overview]
Message-ID: <3d808aa7-3be7-42bf-5548-6ac2d28f7e58@xs4all.nl> (raw)
In-Reply-To: <585d8aea-8e50-e4c7-cb62-e9f62506fba0@gmail.com>

On 12/24/2021 5:45 PM, Jason Ross via ntg-context wrote:
> Dear list,
> 
> Is it possible to set the maximum table of contents depth to a number 
> rather than providing an explicit list of section names?
> 
> 
> Background:
> 
> I am developing an exporter for Org mode. In Org, users can specify the 
> number of levels they want in the table of contents with a number. I 
> currently do this by having the sectioning commands be known to the 
> exporter so I can generate a command like
>      \setupcombinedlist
>        [content]
>        [list={section,subsection}]
> for n=2.
> 
> I'm considering using  \start/stopsectionlevel for sectioning commands 
> instead. That way, users could add \definesectionlevels to the document 
> preamble to use whatever sectioning scheme they wanted. However, this 
> would mean that the exporter wouldn't know what sectioning commands to 
> use the TOC setup.
given the amount of reactions i added a simple levels feature ... the 
best i can do for now is:

\placelist[chapter,section,subsection][levels=2]

keep in mind that all should work with the already present selective 
placement and filtering (criterium)

uploaded

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      parent reply	other threads:[~2021-12-25  0:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-24 16:45 Jason Ross via ntg-context
2021-12-24 17:42 ` Denis Maier via ntg-context
2021-12-24 17:49   ` Denis Maier via ntg-context
2021-12-24 17:53     ` Jason Ross via ntg-context
2021-12-24 21:13       ` Denis Maier via ntg-context
2021-12-24 21:20         ` Denis Maier via ntg-context
2021-12-24 21:22           ` Jason Ross via ntg-context
2021-12-24 21:29             ` Denis Maier via ntg-context
2021-12-24 21:37               ` Jason Ross via ntg-context
2021-12-24 21:43                 ` Denis Maier via ntg-context
2021-12-24 21:48                   ` Denis Maier via ntg-context
2021-12-24 21:55                     ` Jason Ross via ntg-context
2021-12-24 23:35 ` Bruce Horrocks via ntg-context
2021-12-25  0:00 ` Hans Hagen via ntg-context [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=3d808aa7-3be7-42bf-5548-6ac2d28f7e58@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.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).