Re: Problem with showing paths

> uh I missed it...thank you. Also: [...]

Thanks!

By the way, I had a problem compiling MP from the sources. The path of a header file included in a source file was incorrect and it wasn't found. I'll send a proper bug report when I try this again.

Gesendet: Freitag, 21. Januar 2022 um 11:15 Uhr

Von: "luigi scarso" <[email protected]>

An: Kein Empfänger

Cc: "MetaPost List" <[email protected]>

Betreff: Re: [metapost] Problem with showing paths

On Fri, Jan 21, 2022 at 9:52 AM Werner LEMBERG <[email protected] > wrote:

> The problem is the way the lines in the output of "show" are broken:

> The lines are fairly short (max. 80 characters, including the

> newline) and the x- and y-coordinates of the points can be broken

> across two lines, which makes parsing unnecessarily difficult. [...]

>

> Is there anyway to fix this?

Maybe you can send the output to the log file instead, using the

`max_print_line=<length>` environment variable? We use this in

LilyPond.

uh I missed it...thank you. Also:

mpost.w: options->error_line = setup_var (79,"error_line",nokpse);

mpost.w: options->half_error_line = setup_var (50,"half_error_line",nokpse);

mpost.w: options->max_print_line = setup_var (100,"max_print_line",nokpse);

--

luigi

-- http://tug.org/metapost/

--
http://tug.org/metapost/