ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jim <zlists+context@jdvb.ca>
To: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: Table of contents of unnumbered titles
Date: Sat, 9 Sep 2023 18:45:52 -0300	[thread overview]
Message-ID: <ZPznkDvR3Qa6pscH@x360.localdomain> (raw)
In-Reply-To: <e799df32-4088-d58c-261f-2ae687f842f5@gmail.com>

Hi Wolfgang,

On Sat, Sep  9, 2023 at 23:12 (+0200), Wolfgang Schuster wrote:

> Jim schrieb am 09.09.2023 um 22:34:
>> Wolfgang,

>> thanks very much for your help.  As a long-time plain TeX user, but a
>> ConTeXt n00b, that would have taken me a long time to figure out.

>> Having said that (and not to be ungrateful), for both of your examples
>> below, in my tests only the subsubject shows up in the contents. I tried
>> this both with the context distribution (updated a few minutes ago) and
>> with the version that is in texlive (also updated a few minutes ago).  Do
>> all three items show up in your contents listing?

> Hi Jim,

> both examples worked for me without problems and even the online compiler
> on the wiki produces the expected result.  Are you sure all 3 \setuphead
> lines are in your document?

Argh.  Mea culpa.

My mail program did not show me that your first answer had non-breakable
spaces after '[title]' and '[subject]' (but not after '[subsubject]').  And
I quickly copied and pasted those into a file without checking the
character set.  Replacing those with ASCII spaces makes everything work
nicely, thanks very much.

Amusingly (sort of), there was a bun-fight on the texhax mailing list
recently when someone's message came across with non-breakable spaces in
it, causing the recipient to complain that something didn't work, when the
originator vehemently asserted that it did.  (I was neither of those two
people, although I did help the originator trace where the nbsp's got into
his message.)  It's like deja vu all over again.

Did you insert your helpful solution into the wiki somewhere, or just test
them in the wiki compiler?  I just reloaded
and don't see your code there, but since yours does work and those
(apparently) do not work, it would be nice to have your code there.


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

  reply	other threads:[~2023-09-09 21:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-09 18:11 [NTG-context] " Jim
2023-09-09 19:17 ` [NTG-context] " Wolfgang Schuster
2023-09-09 20:34   ` Jim
2023-09-09 21:12     ` Wolfgang Schuster
2023-09-09 21:45       ` Jim [this message]
2023-09-09 19:38 ` Lutz Haseloff
2023-09-10 19:43   ` Jim

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZPznkDvR3Qa6pscH@x360.localdomain \
    --to=zlists+context@jdvb.ca \
    --cc=ntg-context@ntg.nl \
    --cc=wolfgang.schuster.lists@gmail.com \


* 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