ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jason Ross via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Jason Ross <jasonross1024@gmail.com>
Subject: Re: Setting table of contents depth by number rather than by list
Date: Fri, 24 Dec 2021 13:55:34 -0800	[thread overview]
Message-ID: <7aaa742c-331d-e860-3f6d-e7338ab6fabd@gmail.com> (raw)
In-Reply-To: <818516295.476401.1640382485830@office.mailbox.org>

On 12/24/21 1:48 PM, Denis Maier via ntg-context wrote:
> Anyway, I agree that a solution via hierarchy levels would be nice.

That's what I'm hoping to achieve. I'm not familiar enough with 
low-level ConTeXt to do something like this but it seems like it ought 
to be possible.


>> You don't do that. If you provide default a default sectionlevel 
>> scheme, you'll know what toc:2 means.
>> If a user uses a different scheme provided via 
>> #+Context_Section_Levels you can use that to adjust the meaning of 
>> toc:2. But if a user uses the default setting toc:2 should be fine. 
>> Does that make sense?

I understand. The issue I see is that this introduces a coupling between 
section structure and table of contents that could be confusing for 
users, and also makes the interface more complicated by adding another 
keyword.

I am trying to take advantage of the flexibility of ConTeXt for most of 
the configuration, because a user is more likely to be familiar with 
ConTeXt than with my specific elisp module.


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

  reply	other threads:[~2021-12-24 21:55 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 [this message]
2021-12-24 23:35 ` Bruce Horrocks via ntg-context
2021-12-25  0:00 ` Hans Hagen via ntg-context

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=7aaa742c-331d-e860-3f6d-e7338ab6fabd@gmail.com \
    --to=ntg-context@ntg.nl \
    --cc=jasonross1024@gmail.com \
    /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).