From: batela <batela@tugamail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [***SPAM***] Re: last ContextMinimals - bad itemize
Date: Wed, 22 Apr 2009 16:24:52 +0100 [thread overview]
Message-ID: <55954618f0ad66e3f2b1c9986cb23bd0@tugamail.com> (raw)
In-Reply-To: <B17D23BA-8C2C-45CD-BFF2-EADA3CABF3AC@gmail.com>
Dears Sirs,
anybody can share a solution for this bug. I need to prepare a document
for tomorrow and it is very unpleasant include this kind of error.
thanks a lot.
Em 21/04/2009, às 6:09, Wolfgang Schuster escreveu:
>
> Am 21.04.2009 um 18:31 schrieb batela:
>
>> Dear Sirs
>>
>> I found this bug in ContextMinimals last version
>> \starttext
>>
>> \startitemize[n]
>> \item first
>> \item second
>> \startitemize[m,repeat]
>> \item second.1, ===================== should be 2.1, but only appears
>> 1.
>> \item second.2
>> \stopitemize
>> \stopitemize
>>
>> \stoptext
>
> I found a bug in nested items too.
>
> \starttext
> \startitemize
> \startitemize[fit]
> \item subitem
> \stopitemize
> \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://tex.aanhet.net
> archive : https://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> _______________________________________________________________________
> ____________
>
>
Abraços,
Jorge Manuel de Almeida Magalhães
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-04-22 15:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 21:33 new beta Hans Hagen
2009-04-17 1:18 ` Eythan Weg
2009-04-17 7:40 ` Hans Hagen
2009-04-17 7:44 ` Taco Hoekwater
2009-04-17 13:10 ` Eythan Weg
2009-04-17 14:22 ` Hans Hagen
2009-04-17 15:21 ` Eythan Weg
2009-04-17 15:53 ` Taco Hoekwater
2009-04-17 16:41 ` Eythan Weg
2009-04-17 16:48 ` Hans Hagen
2009-04-17 19:03 ` Eythan Weg
2009-04-17 17:36 ` Taco Hoekwater
2009-04-17 19:40 ` Eythan Weg
2009-04-17 1:54 ` Wei-Wei Guo
2009-04-17 9:03 ` Wei-Wei Guo
2009-04-17 11:52 ` Hans Hagen
2009-04-17 11:52 ` Hans Hagen
2009-04-18 0:09 ` Wei-Wei Guo
2009-04-18 0:34 ` Yanrui Li
2009-04-18 0:41 ` Yanrui Li
2009-04-18 2:47 ` Wei-Wei Guo
2009-04-18 11:29 ` Hans Hagen
2009-04-18 17:12 ` Wei-Wei Guo
2009-04-18 19:24 ` Hans Hagen
2009-04-19 0:04 ` Wei-Wei Guo
2009-04-19 9:58 ` Hans Hagen
2009-04-20 22:50 ` Diego Depaoli
2009-04-18 11:56 ` Hans Hagen
2009-04-18 16:49 ` Wei-Wei Guo
2009-04-18 2:25 ` Wei-Wei Guo
2009-04-21 16:31 ` last ContextMinimals - bad itemize batela
2009-04-21 17:09 ` Wolfgang Schuster
2009-04-22 15:24 ` batela [this message]
2009-04-24 15:49 ` [***SPAM***] " batela
2009-04-27 2:36 ` 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=55954618f0ad66e3f2b1c9986cb23bd0@tugamail.com \
--to=batela@tugamail.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).