On Fri, Jul 03, 2020 at 09:56:28PM +0200, Hans Hagen wrote:
> On 7/3/2020 2:55 PM, Marcel Fabian Krüger wrote:
> > Hi,
> >
> > I recently noticed some cases where luametatex behaved in unexpected
> > ways:
> >
> >- The "Extra \fi" error isn't triggered, instead an extra `\fi`
> > freezes
On 7/3/2020 2:55 PM, Marcel Fabian Krüger wrote:
Hi,
I recently noticed some cases where luametatex behaved in unexpected
ways:
- The "Extra \fi" error isn't triggered, instead an extra `\fi`
freezes luametatex. (Can be reproduced by compiling a document which
only consists of a si
On Fri, 3 Jul 2020, Taco Hoekwater wrote:
\hbadness affects reports on stretched/shrunk box glue, but not
overfull boxes. You need \hfuzz for that
\hfuzz = 12pt
Or, for something more drastic:
\dontcomplain
Aditya
_
\hbadness affects reports on stretched/shrunk box glue, but not
overfull boxes. You need \hfuzz for that
\hfuzz = 12pt
Best wishes,
Taco
> On 3 Jul 2020, at 14:53, Hans van der Meer wrote:
>
> I would very much like to get rid of the overfull hbox messages in the log.
> They clutter the log a
Hi,
I recently noticed some cases where luametatex behaved in unexpected
ways:
- The "Extra \fi" error isn't triggered, instead an extra `\fi`
freezes luametatex. (Can be reproduced by compiling a document which
only consists of a single \fi)
- token.new can only create some `data` t
I would very much like to get rid of the overfull hbox messages in the log. They clutter the log and I have not much use for themSetting \hbadness to a large enough value should suppress them below the threshold. But this does not happen. At least not in the minimal example enclosed herby.Is there
On Fri, 3 Jul 2020 08:40:22 +0200
Fabrice Couvreur wrote:
> Thanks, it works but only for a comment and a picture. Indeed, if I
> add a comment and an image, the first image is placed on the second
> comment. Fabrice
>
> \starttext
> \startuserdata[margintext]
> \input ward
> \stopuserdata
> \m
