ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: strange crash
Date: Sat, 18 Feb 2017 13:15:39 +0100	[thread overview]
Message-ID: <CAG5iGsAcSu-38ioGvq8NvzONyUw=0XmaK=n_9k4U2D7nJ4wxXw@mail.gmail.com> (raw)
In-Reply-To: <37C63F5D-40C0-4E3F-9D16-D20751E67C6C@toppkieker.net>

On Sat, Feb 18, 2017 at 12:49 PM, Lutz Haseloff <lutzi@toppkieker.net> wrote:
> Okay, I used the self compiled experimental luatex.
> And so does the luatex from the context minimals behave:
>
> (It is rather old)
>
> root@localhost:~# /usr/local/context/bin/luatex --version
> This is LuaTeX, Version 1.0.0 (TeX Live 2017/dev)
>
> Execute 'luatex --credits' for credits and version details.
>
> There is NO warranty. Redistribution of this software is covered by
> the terms of the GNU General Public License, version 2 or (at your option)
> any later version. For more information about these matters, see the file
> named COPYING and the LuaTeX source.
>
> LuaTeX is Copyright 2016 Taco Hoekwater and the LuaTeX Team.
>
> root@localhost:~# /usr/local/context/bin/luatex --luaonly ~/test.lua
> /home/test.lua:2: bad argument #1 to 'pairs' (table expected, got nil)
> root@localhost:~#
>
>
> It seems, that luatex 1.0.0 can't work with the new context beta.
Hans is fixing mtxrun, but the latest beta works with 1.0.3, backward
compatibility is not assured.

-- 
luigi
___________________________________________________________________________________
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
___________________________________________________________________________________

      parent reply	other threads:[~2017-02-18 12:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 18:51 j. van den hoff
2017-02-16 19:32 ` Alan Braslau
2017-02-16 19:36   ` j. van den hoff
2017-02-16 20:04     ` Marcus Vinicius Mesquita
2017-02-16 20:40 ` Pablo Rodriguez
2017-02-16 20:54   ` Alan Braslau
2017-02-16 20:56     ` j. van den hoff
2017-02-16 21:20       ` Pablo Rodriguez
2017-02-16 21:32         ` j. van den hoff
2017-02-16 21:51           ` Pablo Rodriguez
2017-02-16 22:02       ` Alan Braslau
2017-02-17  9:13 ` Hans Hagen
2017-02-17  9:28   ` Hans Hagen
2017-02-17 10:13     ` strange crash -- SOLVED j. van den hoff
2017-02-17 10:45     ` strange crash Peter Rolf
2017-02-17 13:30       ` luigi scarso
2017-02-17 13:41         ` Peter Rolf
2017-02-18  9:32     ` Lutz Haseloff
2017-02-18  9:50       ` luigi scarso
2017-02-18 10:00         ` Lutz Haseloff
2017-02-18 10:45           ` luigi scarso
2017-02-18 10:59             ` Lutz Haseloff
2017-02-18 11:06               ` luigi scarso
2017-02-18 11:49                 ` Lutz Haseloff
2017-02-18 11:55                   ` luigi scarso
2017-02-18 13:11                     ` Lutz Haseloff
2017-02-18 12:15                   ` luigi scarso [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='CAG5iGsAcSu-38ioGvq8NvzONyUw=0XmaK=n_9k4U2D7nJ4wxXw@mail.gmail.com' \
    --to=luigi.scarso@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).