From: Fabrice Couvreur <fabrice1.couvreur@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: upload
Date: Tue, 28 Jul 2020 10:58:57 +0200 [thread overview]
Message-ID: <CACyK-eoS=9aG8fQdOKXhjF7jE-GB7r2JSOxhSf6DS0Z0Yc24aQ@mail.gmail.com> (raw)
In-Reply-To: <c2b21c49-a6e6-e397-e89b-d74577a7a7f9@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 3667 bytes --]
Hi Hans,
I updated the version of lmtx and wanted to test the following code
\useMPlibrary[dum]
\starttext
\placefigure[right]{}{\externalfigure[dummy]}
\input ward\par
\placefigure[right]{}{\externalfigure[dummy]}
{\bf \input ward} \par
\stoptext
This returns the error message
runtime error : input file 'ward}.tex' is not found, quitting
mtx-context | fatal error: return code: 256
TeX Output exited abnormally with code 1 at Tue Jul 28 10:57:55
Thank you
Fabrice
Le lun. 27 juil. 2020 à 16:42, Hans Hagen <j.hagen@xs4all.nl> a écrit :
> Hi,
>
> Normally we don't report on successive loe level improvements in the
> engine or the core of context (we do so in articles and wrapups), and
> much goes unnoticed anyway (which is good). But ... the last couple of
> weeks we have been playing with some adapted functionality in lmtx and
> some of the experimental low level code has now made it in core.
> Normally users will not notice this but who knows.
>
> There are already features in lmtx that are not (and are unlikely to be)
> in mkiv (most significant in the metapost related part). When possible
> new macros and additions to mechanism will be in both mkiv and lmtx, but
> lmtx users will be better off in the end. We're mostly talking of the
> more tricky mechanisms here, those that currently have limitations due
> to all kind of possible interferences. To summarize:
>
> mkii : frozen (seldom patches)
> lmtx : cutting edge
> mkiv : when possible following lmtx, otherwise frozen
>
> Because we develop lmtx and luametatex alongside it is no problem if we
> have experimental (and even temporary imperfect) code in the engine:
> context knows about it and especially with experiments, we try to make
> sure it doesn't hit users (who we don't expect to use those, often
> undocumented, new tricks anyway). It's sometimes the only way to go
> forward (stepwise testing).
>
> So, here is an example of where lmtx can do better than mkiv:
>
> \placefigure[left]{}{} \input ward \par
> \placefigure[left]{}{} {\bf \input ward} \par
>
> Another area is in using footnotes. As a first step to more robust
> handling of deeply nested notes, lmtx now defaults to (the more than a
> decade optional in mkiv) \automigrateinserts, but with less overhead
> (for performance reasons, it was never enabled in mkiv, apart from
> occasional side effects). It is features like these that will stepwise
> be improved, at least that is what we hope for.
>
> So, the current upload has some new stuff, hopefully without too many
> side effects, but if so, we'll deal with it as usual. As a result, the
> latest lmtx could be a little slower, but I wonder if someone will
> notice it in practice.
>
> 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
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 6344 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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:[~2020-07-28 8:58 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 14:42 upload Hans Hagen
2020-07-28 8:58 ` Fabrice Couvreur [this message]
2020-07-28 11:28 ` upload Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2023-04-11 21:02 upload Hans Hagen via ntg-context
2022-12-21 16:20 upload Hans Hagen via ntg-context
2022-12-21 21:15 ` upload Pablo Rodriguez via ntg-context
2022-12-09 16:41 upload Hans Hagen via ntg-context
2022-10-21 19:23 upload Hans Hagen via ntg-context
2022-07-06 20:10 upload Hans Hagen via ntg-context
2022-07-06 20:38 ` upload Mikael Sundqvist via ntg-context
2022-07-07 1:15 ` upload Max Chernoff via ntg-context
2022-07-07 8:27 ` upload Hans Hagen via ntg-context
2022-07-08 7:40 ` upload Max Chernoff via ntg-context
2022-07-08 14:20 ` upload Hans Hagen via ntg-context
2022-07-07 20:48 ` upload Aditya Mahajan via ntg-context
2022-07-07 21:16 ` upload Hans Hagen via ntg-context
2022-07-08 22:34 ` upload Otared Kavian via ntg-context
2022-07-08 22:40 ` upload Otared Kavian via ntg-context
2022-07-09 7:39 ` upload Hans Hagen via ntg-context
2022-07-09 6:40 ` upload Hans Hagen via ntg-context
2022-05-09 15:41 upload Hans Hagen via ntg-context
2022-05-09 15:54 ` upload mf via ntg-context
2022-05-09 16:16 ` upload Hans Hagen via ntg-context
2022-05-09 16:39 ` upload Alexandre Christe via ntg-context
2022-05-09 16:16 ` upload Alexandre Christe via ntg-context
2022-05-09 16:36 ` upload Mikael Sundqvist via ntg-context
2022-05-10 5:10 ` upload śrīrāma via ntg-context
2022-05-11 12:48 ` upload śrīrāma via ntg-context
2022-05-11 15:46 ` upload Zhichu Chen via ntg-context
2022-05-11 17:00 ` upload Hans Hagen via ntg-context
2022-03-25 10:01 upload Hans Hagen via ntg-context
2022-03-28 21:22 ` upload Otared Kavian via ntg-context
2022-03-28 21:54 ` upload Mikael Sundqvist via ntg-context
2022-03-29 4:37 ` upload Otared Kavian via ntg-context
2022-03-29 14:10 ` upload Mikael Sundqvist via ntg-context
2022-03-29 16:08 ` upload Aditya Mahajan via ntg-context
2022-03-30 10:02 ` upload Otared Kavian via ntg-context
2021-12-30 18:14 upload Hans Hagen via ntg-context
[not found] <mailman.320.1640390435.1172.ntg-context@ntg.nl>
2021-12-25 9:09 ` upload Jeong Dal via ntg-context
2021-12-25 10:57 ` upload Hans Hagen via ntg-context
2021-12-24 18:45 upload Hans Hagen via ntg-context
2021-12-24 22:08 ` upload Jairo A. del Rio via ntg-context
2021-12-24 23:39 ` upload Rik Kabel via ntg-context
2021-12-24 23:54 ` upload Hans Hagen via ntg-context
2021-12-25 9:19 ` upload Marco Patzer via ntg-context
2021-12-25 10:55 ` upload Hans Hagen via ntg-context
2021-12-25 11:22 ` upload Marco Patzer via ntg-context
2021-12-25 11:44 ` upload Hans Hagen via ntg-context
2021-12-25 12:18 ` upload Marco Patzer via ntg-context
2021-12-03 14:29 upload Hans Hagen via ntg-context
2021-12-06 4:41 ` upload Jairo A. del Rio via ntg-context
2021-11-24 14:29 upload Hans Hagen via ntg-context
2021-11-26 10:06 ` upload Alain Delmotte via ntg-context
2021-11-26 10:44 ` upload Hans Hagen via ntg-context
2021-10-21 18:04 upload Hans Hagen via ntg-context
2021-10-21 19:13 ` upload Pablo Rodriguez via ntg-context
2021-10-22 7:55 ` upload Hans Hagen via ntg-context
2021-10-21 20:31 ` upload Mikael Sundqvist via ntg-context
2021-10-22 7:22 ` upload Hans Hagen via ntg-context
2021-10-23 8:10 ` upload Mikael Sundqvist via ntg-context
2021-10-22 15:50 ` upload Michal Vlasák via ntg-context
2021-10-22 16:51 ` upload Pablo Rodriguez via ntg-context
2021-10-23 0:40 ` upload Hans Hagen via ntg-context
2021-10-18 21:17 upload Hans Hagen via ntg-context
2021-10-19 6:43 ` upload Axel Kielhorn via ntg-context
2021-10-20 7:29 ` upload Hans Hagen via ntg-context
2021-10-19 16:03 ` upload Pablo Rodriguez via ntg-context
2020-11-23 17:55 upload Hans Hagen
2020-11-23 18:28 ` upload Pablo Rodriguez
2020-11-23 18:29 ` upload Christian Prim
2020-11-23 19:21 ` upload Otared Kavian
2020-11-23 19:27 ` upload Hans Hagen
2020-11-23 19:24 ` upload Hans Hagen
2020-11-17 11:55 upload Hans Hagen
2020-11-17 13:57 ` upload Pablo Rodriguez
2020-11-17 14:15 ` upload Hans Hagen
2020-11-18 20:29 ` upload Pablo Rodriguez
2020-11-18 22:57 ` upload Hans Hagen
2020-11-17 15:26 ` upload Willi Egger
2020-02-11 16:00 upload Hans Hagen
2020-02-11 16:18 ` upload Floris van Manen
2020-02-11 19:07 ` upload Hans Hagen
2020-02-11 21:09 ` upload Richard Mahoney | Indica et Buddhica
2020-02-13 10:28 ` upload mf
2020-02-13 12:57 ` upload Hans Hagen
2020-02-17 9:39 ` upload mf
2013-03-05 18:18 upload Hans Hagen
2013-03-05 19:45 ` upload Thomas A. Schmitz
2012-07-04 8:56 upload Hans Hagen
2012-07-04 10:40 ` upload Hongwen Qiu
2012-07-04 11:29 ` upload Hans Hagen
2012-07-04 16:02 ` upload Philipp Gesang
2012-06-22 9:37 upload Hans Hagen
2012-06-22 10:10 ` upload Marco
2012-06-22 11:24 ` upload Hans Hagen
2012-06-22 12:19 ` upload Marco
2012-06-19 20:40 upload Hans Hagen
2012-06-20 3:28 ` upload Hongwen Qiu
2012-06-20 14:20 ` upload Hans Hagen
2006-04-07 8:22 upload Hans Hagen
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='CACyK-eoS=9aG8fQdOKXhjF7jE-GB7r2JSOxhSf6DS0Z0Yc24aQ@mail.gmail.com' \
--to=fabrice1.couvreur@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).