ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Taco Hoekwater <taco@elvenkind.com>
Subject: Re: lmtx update
Date: Fri, 31 Jul 2020 12:18:51 +0200	[thread overview]
Message-ID: <68e4a562-f2b0-21e5-9787-456f2694a9c7@xs4all.nl> (raw)
In-Reply-To: <F51866AB-E02A-431A-B519-64A193BB646D@elvenkind.com>

On 7/31/2020 10:40 AM, Taco Hoekwater wrote:
> Hi Hans,
> 
>> On 31 Jul 2020, at 10:32, Hans Hagen <j.hagen@xs4all.nl> wrote:
>>
>> Hi,
>>
>> Sorry for the long mail ...
>>
>> One of the changes in lmtx is that we freeze the properties that determine the paragraph shape as well as breaking into lines in such a way that we have predictable behaviour. As a side effect it can be that existing code (lmtx only) will behave differently (will be fixed when we notice) but also that some low level user tweaking can not work, i.e. they are just ignored, but only when they happen mid paragraph which actually is always debatable anyway.
>>
>> Now, if for some reasom you get unexpected results and can't wait for a fix, you can do this:
>>
>>   \forgetparagraphfreezing : disables
>>   \setparagraphfreezing    : enables (default)
> 
> Are those global or local or can they be prefixed? For example, can we do this:
> 
>    \setparagraphfreezing
>    ….
>    \placefigure[left]{}{} {Bla bla \forgetparagraphfreezing .. <override some stuff> }

the forget will basically tell the system that it should use the normal 
(register) variables ... a freeze stores values in the local par node 
but also stores which parameters are stored, so it is selective (one can 
  freeze specific ones

\snapshotpar \frozenhangaftercode

which now makes me think: i can let a negative value do a specific 
unfreeze (\snapshotpar0 will unfreeze all)

> or would that still trigger the built-in freeze ?

the (enabled by default) stored the values right after the par has started

\setparagraphfreezing

so then these values are frozen

a successive change is then not used, but say that you do

\parfillskip100pt

in the middle of a paragraph, then that one will affect the next paragraph

\bgroup
\frozen \parfillskip100pt
\egroup

when this is done inside a paragraph, the assignment is done local, then 
it gets frozen in the current paragraph but it will not affect the next 
paragraph unless of course you used \global

(\frozen is just a prefix and when it's time to do an assignment, just 
like the global state is checked, the frozen state is checked, and 
applied after the normal assignment, of course only for variables that 
deal with the par buildingl it is ignored otherwise; so, \frozen also 
works here: \frozen\advance\leftskip 10pt\relax)

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
___________________________________________________________________________________

  reply	other threads:[~2020-07-31 10:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-31  8:32 Hans Hagen
2020-07-31  8:40 ` Taco Hoekwater
2020-07-31 10:18   ` Hans Hagen [this message]
2020-08-01 13:20 ` Otared Kavian
2020-08-01 14:17   ` Hans Hagen
2020-08-01 16:20     ` Otared Kavian
2020-08-01 16:41   ` Henning Hraban Ramm
2020-08-01 16:57     ` Otared Kavian
2020-08-01 17:19       ` margin notes (was: lmtx update) Henning Hraban Ramm
2020-08-01 20:36         ` Otared Kavian
2020-08-01 21:01           ` Henning Hraban Ramm
2020-08-01 21:35             ` Otared Kavian
2020-08-02  3:30 ` lmtx update Aditya Mahajan
2020-08-03 17:37 ` Pablo Rodriguez
2020-09-16 15:52 ebohoyod
2020-09-16 16:23 ` Wolfgang Schuster
     [not found]   ` <6f2953c3-4b09-e824-da78-46347ef5f4af@disroot.org>
2020-09-17  8:14     ` Eduardo Bohoyo
2020-09-17 10:35       ` Wolfgang Schuster
2020-09-17 10:50         ` Eduardo Bohoyo
2020-09-17 11:11           ` Eduardo Bohoyo
2021-08-19 17:57 Hans Hagen via ntg-context
2021-08-19 20:07 ` Aditya Mahajan via ntg-context
2021-08-20  5:52   ` Hans Hagen via ntg-context
     [not found] <mailman.0.1629453601.23792.ntg-context@ntg.nl>
2021-08-22 22:55 ` Benjamin Buchmuller via ntg-context
2021-08-23  6:21   ` Hans Hagen via ntg-context
2023-02-06 17:21 Hans Hagen via ntg-context

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=68e4a562-f2b0-21e5-9787-456f2694a9c7@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=taco@elvenkind.com \
    /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).