ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: context@vivaldi.net
To: ConTeXt <ntg-context@ntg.nl>
Subject: Re: Strange error with combination of itemization, footnote and \crlf
Date: Thu, 31 Oct 2019 11:43:55 +0100	[thread overview]
Message-ID: <c0c5d22877156fa272b797365930c62c@vivaldi.net> (raw)
In-Reply-To: <2b102232-c6a1-ea90-6b29-a41e7ba5ff13@xs4all.nl>

Hello Hans,

when do you plan to release next beta for ConTeXt with the fixed issue 
spoken bellow?

Normally, one can get beta here:

	http://www.pragma-ade.nl/download-2.htm

but there is still beta from 2019-10-29.

(I'm still using Lua 5.3 version of ConTeXt.)

Or is it enough to re-run "first-setup.bat" from the ConTeXt 
installation directory, which uses "rsync" (points to 
"rsync://contextgarden.net/minimals/setup/mswin/bin/" and launches 
"mtxrun --script ./bin/mtx-update.lua")?

Best regards,

Lukas


On 2019-10-22 23:54, Hans Hagen wrote:
> On 10/22/2019 2:16 PM, context@vivaldi.net wrote:
>> Hello,
>> 
>> here is a minimal sample which doesn't compile:
>> 
>> ----
>> \starttext
>>    \startitemize
>>      \item
>>        A\footnote{%
>>          B
>>          \startitemize
>>            \item C
>>          \stopitemize
>>        }\crlf
>>        D
>> 
>>      \item E % <<<< This sample compiles when this line is commented 
>> (?!)
>>    \stopitemize
>> \stoptext
>> ----
>> 
>> The error message is:
>> 
>> "
>> ...
>> ...eta/tex/texmf-context/tex/context/base/mkiv/strc-num.lua:465: 
>> attempt to index a nil value (local 'd')
>> 
>>   2       \startitemize
>>   3         \item
>>   4           A\footnote{%
>>   5             B
>>   6             \startitemize
>>   7               \item C
>>   8             \stopitemize
>>   9           }\crlf
>> 10           D
>> 11
>> 12 >>      \item E % <<<< This sample compiles when this line is 
>> commented
>> 13       \stopitemize
>> 14     \stoptext
>> 15
>> "
>> 
>> When the "\item E" is commented, the sample compiles successfully.
>> 
>> ConTeXt version: "ConTeXt  ver: 2019.10.11 15:47 MKIV beta  fmt: 
>> 2019.10.16  int: english/english".
>> 
>> Any idea what's going wrong?
> side effect of recent attempt to deal with nesting ... fixed in next 
> beta
> 
> -----------------------------------------------------------------
>                                           Hans Hagen | PRAGMA ADE
>               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>        tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2019-10-31 10:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22 12:16 context
2019-10-22 21:54 ` Hans Hagen
2019-10-31 10:43   ` context [this message]
2019-11-04 17:31     ` Pablo Rodriguez

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=c0c5d22877156fa272b797365930c62c@vivaldi.net \
    --to=context@vivaldi.net \
    --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).