From: Max Chernoff via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Max Chernoff <mseven@telus.net>
Subject: Re: Missing parinitskips in \normalizelinemode=0
Date: Wed, 26 Oct 2022 21:48:42 -0600 [thread overview]
Message-ID: <50eb03490b4a97ff167686ce4514cd127504c439.camel@telus.net> (raw)
In-Reply-To: <ace30992-d1aa-9287-d6a7-df7cabfa2c1b@freedom.nl>
Hi Hans,
> i'll bypass that warnign when the mode is zero
I saw that you made that change in the latest upload, thanks.
Unfortunately, I'm still getting the same output:
luatex warning > linebreak: list seems already prepared
luatex warning > linebreak: [ leftinit | rightinit | leftfill | rigthfill ] expected
nil
Also, what's causing me issues isn't the warning but rather that
tex.linebreak is returning nil instead of an info table as the second
return value.
> btw, you need to work with a copy of the list
Now that you point that out, I'm actually surprised that that example
worked at all. The real code does use a copy of the list though (and
also uses the proper callback interfaces instead of "system.callbacks.
permitoverloads")
Thanks,
-- Max
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2022-10-27 3:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 1:01 Max Chernoff via ntg-context
2022-10-19 9:59 ` Hans Hagen via ntg-context
2022-10-27 3:48 ` Max Chernoff via ntg-context [this message]
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=50eb03490b4a97ff167686ce4514cd127504c439.camel@telus.net \
--to=ntg-context@ntg.nl \
--cc=mseven@telus.net \
/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).