From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Sylvain Hubert <champignoom@gmail.com>
Subject: Re: Bug: context/mtxrun makes Firefox eat up cpu
Date: Thu, 29 Oct 2020 16:04:00 +0100 [thread overview]
Message-ID: <b22b66a0-bfd3-0dab-41f8-d921573a0571@xs4all.nl> (raw)
In-Reply-To: <CACNy3NC99OVi7c4zMPh2eYH7J+aNs=HN6aKOnRtMoF=+v4Xb=Q@mail.gmail.com>
On 10/29/2020 3:18 PM, Sylvain Hubert wrote:
> I would consider it more constructive to admit the existence of the bug
> and find a way look into the source code of luametatex, since `context
> --help` is obviously not a terribly complicated routine to investigate.
As taco mentioned, it's very unlikely an engine issue esp as firefox is
somehow involved. A tex engine really does nothing special; just openign
a few files.
What is your test file?
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:[~2020-10-29 15:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 10:29 Sylvain Hubert
2020-10-29 11:00 ` Taco Hoekwater
2020-10-29 11:15 ` Sylvain Hubert
2020-10-29 11:19 ` Sylvain Hubert
2020-10-29 11:31 ` Taco Hoekwater
2020-10-29 11:44 ` Sylvain Hubert
2020-10-29 12:55 ` Taco Hoekwater
2020-10-29 14:14 ` Sylvain Hubert
2020-10-29 15:38 ` Taco Hoekwater
2020-10-29 16:44 ` Sylvain Hubert
2020-10-29 17:15 ` Hans Hagen
2020-10-29 14:18 ` Sylvain Hubert
2020-10-29 15:04 ` Hans Hagen [this message]
2020-10-30 8:34 ` ntg
2020-10-30 9:06 ` Taco Hoekwater
2020-10-30 18:44 ` Sylvain Hubert
2020-10-30 19:14 ` Sylvain Hubert
2020-10-30 19:26 ` Hans Hagen
2020-10-30 18:48 ` Sylvain Hubert
2020-10-30 19:28 ` Hans Hagen
2020-10-29 11:26 ` Sylvain Hubert
2020-10-29 15:48 ` Aditya Mahajan
2020-10-29 16:56 ` Sylvain Hubert
2020-11-04 15:01 ` Sylvain Hubert
2020-11-05 10:48 ` Sylvain Hubert
2020-11-05 11:01 ` Taco Hoekwater
2020-11-05 11:49 ` Sylvain Hubert
2020-11-05 11:25 ` 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=b22b66a0-bfd3-0dab-41f8-d921573a0571@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=champignoom@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).