ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug in startitemize
Date: Mon, 7 Mar 2016 21:23:10 +0100	[thread overview]
Message-ID: <EF754BDF-C287-4DB8-8EBA-EB396E1936DA@gmail.com> (raw)
In-Reply-To: <56DDDAB1.8040604@gmail.com>

Thanks Wolfgang,

Your patch does indeed solve the problem, after rebuilding with

	context --make —all

Best regards: OK

> On 07 Mar 2016, at 20:46, Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:
> 
>> Otared Kavian 7. März 2016 um 20:28
>> Hi Hans,
>> 
>> It seems that with the new beta (ConTeXt ver: 2016.03.04 10:39 MKIV beta fmt: 2016.3.7), there is a bug with random itemization.
>> I cannot tell exactly when this feature has been broken.
>> The problem is that for instance in the following example, sometimes the item C is repeated three times, sometimes A is repeated twice, etc.
> strc-itm.mkvi:
> 
> \def\strc_itemgroups_collected_flush
>   {\ifconditional\c_strc_itemgroups_randomize
>      \getrandomcount\c_strc_itemgroups_collected_current\plusone\c_strc_itemgroups_collected_stored
>    \else
>      \advance\c_strc_itemgroups_collected_current\plusone
>    \fi
>    \ifcsname\??itemgroupstack\number\c_strc_itemgroups_collected_current\endcsname
>      \edef\collecteditemgroupitem{\lastnamedcs}%
>      \ifconditional\c_strc_itemgroups_horizontal
>        \strc_itemgroups_collected_flush_horizontal
>      \else
>        \collecteditemgroupitem
> +      \letbeundefined{\??itemgroupstack\number\c_strc_itemgroups_collected_current}%
>      \fi
>      \advance\c_strc_itemgroups_collected_done\plusone
>    \fi
>    \ifnum\c_strc_itemgroups_collected_done<\c_strc_itemgroups_collected_stored
>      \expandafter\strc_itemgroups_collected_flush
>    \fi}
> 
> 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
> ___________________________________________________________________________________

___________________________________________________________________________________
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:[~2016-03-07 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07 19:28 Otared Kavian
2016-03-07 19:46 ` Wolfgang Schuster
2016-03-07 20:23   ` Otared Kavian [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=EF754BDF-C287-4DB8-8EBA-EB396E1936DA@gmail.com \
    --to=otared@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).