ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Pawel Jackowski na Onet" <jackos1@poczta.onet.pl>
Subject: Re: Re: uncompatibility?
Date: Wed, 15 Oct 2003 01:36:55 +0200	[thread overview]
Message-ID: <006801c392ac$16a702a0$1c00a8c0@best> (raw)
In-Reply-To: <6.0.0.22.2.20031014215123.02d27ac0@localhost>

Problem: a (very) different ConTeXt versions and a different output

From: "Hans Hagen" <pragma@wxs.nl>
To: <ntg-context@ntg.nl>
Sent: Tuesday, October 14, 2003 9:52 PM


> At 17:36 11/10/2003, you wrote:
>
> >Lets consider the following code:
> >
> >\setupitemize[4,packed]
> >\starttext
> >\startitemize[n]
> >  \item one
> >  \item two
> >  \item three
> >\stopitemize
> >\stoptext
> >
> >The problem is that in newer installation, default itemize style (meaning
> >packed, with triangle symbol) IS FORCED instead of style given direclty
> >(just numbering). The older one do what I would expect; numbered style
has a
>
> hm, i'll look into it; it's probably related to the fact that last year
> itemize became definable and retaining downward compatibility for the
> \setupitemize command was tricky

Thanks in advance. The simplest way to customize that code to suit the fresh
context versions is to comment first line, so I can live with it.




Pawe/l

  reply	other threads:[~2003-10-14 23:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-11  7:29 uncompatibility? Pawel Jackowski na Onet
2003-10-11  9:09 ` uncompatibility? Patrick Gundlach
2003-10-11  9:34   ` uncompatibility? Hans Hagen
2003-10-11 15:36     ` Pawel Jackowski na Onet
2003-10-11 16:48       ` uncompatibility? Patrick Gundlach
2003-10-12  6:26         ` uncompatibility? Pawel Jackowski na Onet
2003-10-12  9:59           ` uncompatibility? Patrick Gundlach
2003-10-14 19:43             ` uncompatibility? Hans Hagen
2003-10-14 19:47           ` Hans Hagen
2003-10-14 19:52       ` Hans Hagen
2003-10-14 23:36         ` Pawel Jackowski na Onet [this message]
2003-10-14 21:29       ` Hans Hagen

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='006801c392ac$16a702a0$1c00a8c0@best' \
    --to=jackos1@poczta.onet.pl \
    --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).