ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Kevin D. Robbins" <robbins.kevin.d@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem or bug with enumerations in latest ConTeXt beta
Date: Mon, 26 Oct 2009 12:10:00 -0600	[thread overview]
Message-ID: <f5d0b64b0910261110m2bd84b05pef25f0cf4fd718a4@mail.gmail.com> (raw)
In-Reply-To: <4AE2FC2B.6040908@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1725 bytes --]

Hi Hans,

Thanks for the quick fix! I retested with the latest from minimals, and all
three problems I reported are fixed.

Kevin

On Sat, Oct 24, 2009 at 7:07 AM, Hans Hagen <pragma@wxs.nl> wrote:

> Kevin D. Robbins wrote:
>
>> Hello all,
>>
>> I have attached a fairly minimal example that demonstrates three problems
>> I currently have using an enumeration for code listings.
>>
>> The first problem is that \placelist[enumeration:listing] errors out with:
>>
>
> has to do with the fact that the list is not initialized (i'll add a test
> for that) and therefore variables are not resolved using the parent chain
>
> for the moment add:
>
>  \definelist[listing]
>
> also, use "listing' as name in order to get some result
>
>  \setuplist[listing]...
>
>  \placelist[listing][criterium=text]
>
> Hans
>
> -----------------------------------------------------------------
>                                          Hans Hagen | PRAGMA ADE
>              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
>                                             | www.pragma-pod.nl
> -----------------------------------------------------------------
>
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 2878 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 bytes --]

___________________________________________________________________________________
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:[~2009-10-26 18:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-22  0:12 Kevin D. Robbins
2009-10-24 13:07 ` Hans Hagen
2009-10-26 18:10   ` Kevin D. Robbins [this message]

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=f5d0b64b0910261110m2bd84b05pef25f0cf4fd718a4@mail.gmail.com \
    --to=robbins.kevin.d@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).