ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Thoughts about counters
Date: Wed, 20 Oct 2010 17:11:32 +0200	[thread overview]
Message-ID: <2F38E738-80EA-4301-989F-CEDA45FEF95D@gmail.com> (raw)
In-Reply-To: <4CBEF9DB.2080702@amolf.nl>


Am 20.10.2010 um 16:16 schrieb Bela Mulder:

> Wolfgang: thanks for the tips, I'll try them out.

Be aware that prefix/numbersegments is only available in mkiv.

> Hans: Here is the example, which produced the output in my Thoughts document (http://dl.dropbox.com/u/5718469/counters.pdf)
> 
> \definetyping[cmds]
> \setuptyping[cmds][option=commands]
> \starttext
> \startcmds \def\MySectionCounter{P\currentcounter[part].C\currentcounter[chapter]-\currentcounter[section]}
>    /stopcmds
> \stoptext
> 
> which has inserted spaces before the opening square brackets and between e.g. \def and \MySectionCounter.

Can’t reproduce your problem here (using latest minimals) neither with mkii
nor with mkiv but why do you write „/stopcmds“ and not „\stopcmds“?

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:[~2010-10-20 15:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20 14:16 Bela Mulder
2010-10-20 15:11 ` Wolfgang Schuster [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-10-20  9:59 Bela Mulder
2010-10-20 11:57 ` Hans Hagen
2010-10-20 13:09 ` Wolfgang Schuster

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=2F38E738-80EA-4301-989F-CEDA45FEF95D@gmail.com \
    --to=schuster.wolfgang@googlemail.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).