From: Willi Egger via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Willi Egger <w.egger@boede.nl>
Subject: Re: \writetolist not writing the number to the TOC
Date: Sun, 26 Mar 2023 15:10:11 +0200 [thread overview]
Message-ID: <5406A55B-9B1D-406C-B9CE-B46D19539C0C@boede.nl> (raw)
In-Reply-To: <4cc7f52d-15d5-ac8a-b882-6aa79bf0db2c@fiee.net>
Hello Hraban,
thank you. I missed this point. However, adding a dot behind the number does not appear to solve the problem. The title’s text still starts at the left margin which looks very odd.
Kind regards
Willi
> On 26 Mar 2023, at 12:51, Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl> wrote:
>
> Am 25.03.23 um 23:05 schrieb Willi Egger via ntg-context:
>> Good evening!
>> I have a setup in which I need to send info to the TOC:
>> Consider the following example:
>> \starttext
>> \starttitle[title=Contents]
>> \placelist[chapter][criterium=all]
>> \stoptitle
>> \startchapter[title=Mychapter]
>> \input knuth
>> \startsubject[title=Subject will be in TOC]
>> \writetolist[chapter]{1}{I am in TOC!}
>> \input ward
>> \stopsubject
>> \stopchapter
>> \stoptext
>> According to the Wiki I should get te number (1) in the TOC. Instead the text starts at the height of the chapter-numbering and is not carrying the given number.
>> Am I doing something wrong?
>
> The wiki says:
>
> “The default table of contents is combined list. To write to it one has to choose the level to which it should be inserted: \writetolist[chapter]{1.}{Chapter list entry A},
> \writetolist[section]{1.1}{Section list entry A}, etc.”
>
> https://wiki.contextgarden.net/Command/writetolist
>
> So maybe you need a dot?
>
> Otherwise I don’t know.
>
> Hraban
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-03-26 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 22:05 Willi Egger via ntg-context
2023-03-26 10:51 ` Henning Hraban Ramm via ntg-context
2023-03-26 13:10 ` Willi Egger via ntg-context [this message]
2023-03-27 13:52 ` Hans Hagen via ntg-context
2023-03-27 15:13 ` Willi Egger 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=5406A55B-9B1D-406C-B9CE-B46D19539C0C@boede.nl \
--to=ntg-context@ntg.nl \
--cc=w.egger@boede.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).