ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \head: broken?
Date: Wed, 16 Jul 2014 14:52:39 +0200	[thread overview]
Message-ID: <C0A341F6-101E-48DA-8CB3-DE2BB966A24B@gmail.com> (raw)
In-Reply-To: <dcd951f16634ec28361910843aef7f76.squirrel@webmail.xs4all.nl>


Am 16.07.2014 um 13:07 schrieb Rob Heusdens <robheus@xs4all.nl>:

> Hello All,
> 
> Still having problem with \head in \setupitemize.
> 
> - When I set the headstyle in \setupitemize, the numbering disappears and
> the symbol appear (like when I used '1' instead of 'n'). (ex. 1: MNWE)
> 
> - If I comment the headstyle out, numbers do appear. (ex. 2: MWE).
> 
> Why is that?

You can’t mix keywords and assignment in the same argument of a setup-command, e.g.

    \staritemize[packed,headstyle=bold]

but some commands have multiple arguments which you use for both types, e.g.

    \startitemize[packed][headstyle=bold]

BTW: A minimal example should be compilable (i.e. you need \starttext and \stoptext) which isn’t the case with your example.

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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2014-07-16 12:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16 11:07 Rob Heusdens
2014-07-16 12:52 ` Wolfgang Schuster [this message]
2014-07-18 11:05   ` Rob Heusdens
  -- strict thread matches above, loose matches on Subject: below --
2014-07-12 23:11 Rob Heusdens
2014-07-12 23:32 ` Aditya Mahajan

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=C0A341F6-101E-48DA-8CB3-DE2BB966A24B@gmail.com \
    --to=schuster.wolfgang@gmail.com \
    --cc=ntg-context@ntg.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).