From: Benjamin Buchmuller via ntg-context <ntg-context@ntg.nl>
To: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Cc: Benjamin Buchmuller <benjamin.buchmuller@gmail.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with \head inside \itemize
Date: Thu, 23 Dec 2021 09:06:21 +0100 [thread overview]
Message-ID: <1C43DDF6-FCCC-46AD-A61C-C66375A3A9CF@gmail.com> (raw)
In-Reply-To: <db6177ff-d8b3-76f2-9bd0-9e172b89d77d@gmail.com>
Thanks, Wolfgang, perfectly works! I added an example to the Wiki.
> On Dec 21, 2021, at 18:03, Wolfgang Schuster <wolfgang.schuster.lists@gmail.com> wrote:
>
> Benjamin Buchmuller via ntg-context schrieb am 21.12.2021 um 14:04:
>> Not sure if this is the behavior to expect, but I would like to get formatted inline headers in itemize like:
>
> The syntax for \starthead is
>
> \starthead {...} ... \stophead
>
> where the argument within the braces is mandatory.
>
>> – Unformatted item.
>> – *Head One.* Something bla bla.
>> – *Head Two.* Other bla bla.
>>
>> From:
>>
>> \setupitemize[each][2, headintext]
>> % \setupitemize[each][headstyle={\groupedcommand{\bf}{.\space\tf}}]
>> \setupitemize[each][headcolor=red, headstyle=bold]
>>
>> \startitemize
>> \item Unformatted item.
>> \head Head One \par Something bla bla.
>> \starthead Head Two \stophead Other bla bla. % Even worse: No inline any more.
>> \stopitemize
>>
>> However, headstyle= and headcolor= seem to spill all over … Is it a feature or a bug?
>
> No bug, just a user error. When you put the head text in the argument of \starthead everything works as expected.
>
> \starttext
>
> \startitemize[headintext][headstyle=bold]
> \startitem Unformatted item. \stopitem
> \starthead {Head One.} Something bla bla. \stophead
> \starthead {Head Two.} Other bla bla. \stophead
> \stopitemize
>
> \stoptext
>
> 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-12-23 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 13:04 Benjamin Buchmuller via ntg-context
2021-12-21 17:03 ` Wolfgang Schuster via ntg-context
2021-12-23 8:06 ` Benjamin Buchmuller via ntg-context [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-22 13:15 Jean-Philippe Rey via ntg-context
2021-11-22 13:30 ` Taco Hoekwater via ntg-context
2021-11-22 14:59 ` 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=1C43DDF6-FCCC-46AD-A61C-C66375A3A9CF@gmail.com \
--to=ntg-context@ntg.nl \
--cc=benjamin.buchmuller@gmail.com \
--cc=wolfgang.schuster.lists@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).