From: Hans Hagen <pragma@wxs.nl>
To: "j. van den hoff" <veedeehjay@gmail.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: yearly current
Date: Wed, 15 Feb 2017 22:00:52 +0100 [thread overview]
Message-ID: <bb7e7448-6c83-eff6-7cc7-809b30c6c6c5@wxs.nl> (raw)
In-Reply-To: <op.yvpvz7d4kcdbg5@muck.fritz.box>
On 2/15/2017 8:49 PM, j. van den hoff wrote:
> On Wed, 15 Feb 2017 20:08:53 +0100, Hans Hagen <pragma@wxs.nl> wrote:
>
>> Hi,
>>
>> We're getting close to tex live freeze and part of that process is a
>> luatex release as well as a context snapshot. There have been no betas
>> for a while and the reason is that I've been cleaning up some code as
>> well as optimizing some bits. As a consequence it could be that there
>> are some issues with an upcoming luatex / context pair but because
>> there has been no real fundamental changes in the typesetting part
>> problems will be easy to sort out (like using an undefine lua function
>> or so).
>>
>> Anyway, if you are not that adventurous or depend on the current
>> version, you can best make a copy or not update from the garden too
>> eager, just wait till the lists reports no crashes.
>>
>> We will try to fix luatex/context things as fast as possible,
>
> hi,
>
> it _might_ be that I have been just bitten by this (or it is completely
> unrelated ;-)): I have previously installed standalone context on a mac
> w/o problems and am using it just fine.
>
> but today I moved my current document project to a ubuntu machine for
> testing purposes. since there seems to be only an ancient `context'
> provided via apt-get (from 2015) I just installed the standalone on the
> ubuntu machine, too, following the instructions as good I could. context
> and luatex point to the executables in
> /usr/local/context/tex/texmf-linux-64/bin etc.
>
> so it _seems_ to be set up correctly: but the compile run for the
> document (compiling just fine on the mac/older context installation)
> crashes on the ubuntu with a last line:
>
> clearontext | fatal error: no return code, message: luatex:
> execution interrupted
>
> (w/o trailing linefeed, too...).
>
> if I can provide further info, please let me know.
it depends ... we're talking about luatex 1.0.3 (not on the garden yet)
and a not yet published context update ... so it must be something
different at your end
Hans
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2017-02-15 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 19:08 Hans Hagen
2017-02-15 19:49 ` j. van den hoff
2017-02-15 21:00 ` Hans Hagen [this message]
2017-02-15 21:05 ` j. van den hoff
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=bb7e7448-6c83-eff6-7cc7-809b30c6c6c5@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=veedeehjay@gmail.com \
/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).