From: Rik Kabel <ConTeXt@rik.users.panix.com>
To: ntg-context@ntg.nl, Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: LMTX, BIdi, full paragraph, and spurious empty line
Date: Thu, 24 Jun 2021 08:54:26 -0400 [thread overview]
Message-ID: <e9d01ab0-b7a5-bbef-d91c-a52c1635c5ed@rik.users.panix.com> (raw)
In-Reply-To: <d82ddc5c-07d5-638b-cd9a-ba9ecd669202@rik.users.panix.com>
On 6/23/2021 19:44, Rik Kabel wrote:
>
>
> On 6/23/2021 18:10, Hans Hagen wrote:
>> On 6/22/2021 4:52 AM, Rik Kabel wrote:
>>> [...]ome an alternative way to do that.)
>> I'll send you a possible fix but it needs a bit of testing. It has to
>> do with (probably spurious) spaces which means that the parbuilder
>> then considers the dir node to be a reasoable breakpoint (well, kin
>> dof okay as one gets what one asks for), but I'll be a bit more
>> agressive in dealing with that.
>>
>> Hans
>>
> Thank you, Hans, for looking into this so soon.
>
> [...]
Hans and all,
I mistakenly put the new code in the wrong instance. When I put it in
the right place and remade ConTeXt, all is well as far as my test
examples go and the spurious lines are gone.
Thank you for the fix.
--
Rik
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2021-06-24 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 2:52 Rik Kabel
2021-06-23 22:10 ` Hans Hagen
2021-06-23 23:44 ` Rik Kabel
2021-06-24 12:54 ` Rik Kabel [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=e9d01ab0-b7a5-bbef-d91c-a52c1635c5ed@rik.users.panix.com \
--to=context@rik.users.panix.com \
--cc=j.hagen@xs4all.nl \
--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).