From: "Jairo A. del Rio" <jairoadelrio6@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: lmtx
Date: Fri, 30 Oct 2020 21:50:49 -0500 [thread overview]
Message-ID: <CAKyqqaaJ5x9b7KsTa4_+c8rAgbqq3r-iZ4vo0v79EEM8NgiBTQ@mail.gmail.com> (raw)
In-Reply-To: <5afea95a-7473-a15c-5dae-31afcf06e4c4@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 3776 bytes --]
Hi, Hans. The last release is considerably faster for smaller documents
(for larger documents differences seem to be neglectable). Thank you for
such an improvement. However, something is wrong with one manual:
luametatex manual won't compile:
156 Beware: the values are always saved in the format, independent of
the setting
157 of \prm {savinghyphcodes} at the moment the format is dumped.
158
159 A boundary node normally would mark the end of a word which
interferes with for
160 instance discretionary injection. For this you can use the \prm
{wordboundary}
161 as a trigger. Here are a few examples of usage:
162
163 \startbuffer
164 discrete---discrete
165 \stopbuffer
166 >> \typebuffer \startnarrower \dontcomplain \hsize 1pt \getbuffer \par
\stopnarrower
167 \startbuffer
168 discrete\discretionary{}{}{---}discrete
169 \stopbuffer
170 \typebuffer \startnarrower \dontcomplain \hsize 1pt \getbuffer \par
\stopnarrower
171 \startbuffer
172 discrete\wordboundary\discretionary{}{}{---}discrete
173 \stopbuffer
174 \typebuffer \startnarrower \dontcomplain \hsize 1pt \getbuffer \par
\stopnarrower
175 \startbuffer
176 discrete\wordboundary\discretionary{}{}{---}\wordboundary
discrete
A number should have been here; I inserted '0'. (If you can't figure out
why I
needed to see a number, look up 'weird error' in the index to The TeXbook.)
The prepackaged PDF manual is also broken: an error banner.
Regards,
Jairo :)
El vie., 30 de oct. de 2020 a la(s) 17:29, Hans Hagen (j.hagen@xs4all.nl)
escribió:
> Hi,
>
> I might have uploaded a new version by accident so be careful when you
> update. Make a backup first. Sorry,
>
> The test suite compiles, which doesn't day all is ok as i just run it.
>
> There are no funcional changes, only a bit of conceptual reworking of
> some internals in the process of adapting to new features as well as
> protection, so
>
> \starttext
>
> \start
> \def\framed{oeps}
> \stop
>
> \stoptext
>
> is permitted, but when you run with
>
> context --overloadmode=warning
>
> you get a warning and with
>
> context --overloadmode=error
>
> the run aborts. Here is a user macro example:
>
> \frozen \def\foo{oeps}
> \def\foo{oeps} % warning or error
> \overloaded\def\foo{oeps} % okay
>
> eventually all system macros will be way more protected, being
> primitive, permanent, immutable to mention some of the possible
> properties. It's work in progress as you can imagine some pitfals and in
> order for it to work well quite some has to be flagged. Also, I have to
> play with some related additions.
>
> (This version also makes more extensive use of some new macro features
> but that's for later.)
>
> 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: 5059 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-10-31 2:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 22:29 lmtx Hans Hagen
2020-10-31 2:50 ` Jairo A. del Rio [this message]
2020-11-02 19:43 ` lmtx Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2022-02-03 21:00 lmtx Hans Hagen via ntg-context
2021-02-19 12:32 lmtx Hans Hagen
2021-01-18 18:20 lmtx Hans Hagen
2021-01-19 10:57 ` lmtx Floris van Manen
2021-01-19 11:10 ` lmtx Hans Hagen
2021-01-19 11:31 ` lmtx Jano Kula
2021-01-19 19:12 ` lmtx Jan U. Hasecke
2021-01-19 23:03 ` lmtx Hans Hagen
2020-06-19 10:11 lmtx Hans Hagen
[not found] <mailman.1.1576234801.28358.ntg-context@ntg.nl>
2019-12-13 19:29 ` lmtx Jeong Dal
[not found] <mailman.310.1576128525.1207.ntg-context@ntg.nl>
2019-12-12 23:48 ` lmtx Jeong Dal
2019-12-13 8:39 ` lmtx Otared Kavian
2019-12-12 0:37 lmtx Hans Hagen
2019-12-12 5:28 ` lmtx Otared Kavian
2019-12-12 6:04 ` lmtx Otared Kavian
2019-12-12 10:08 ` lmtx Hans Hagen
2019-12-12 6:36 ` lmtx Richard Mahoney | Indica et Buddhica
2019-12-12 16:59 ` lmtx Pablo Rodriguez
2019-12-12 20:13 ` lmtx Pablo Rodriguez
2019-08-05 12:38 lmtx Hans Hagen
2019-04-02 9:05 lmtx Hans Hagen
2019-04-02 19:03 ` lmtx Taco Hoekwater
2019-04-02 20:11 ` lmtx Henri Menke
2019-04-02 20:19 ` lmtx Hans Hagen
2019-04-02 20:30 ` lmtx Henri Menke
2019-04-02 20:47 ` lmtx 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=CAKyqqaaJ5x9b7KsTa4_+c8rAgbqq3r-iZ4vo0v79EEM8NgiBTQ@mail.gmail.com \
--to=jairoadelrio6@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).