* lmtx update/t-vim (again)
[not found] <mailman.0.1629453601.23792.ntg-context@ntg.nl>
@ 2021-08-22 22:10 ` Benjamin Buchmuller via ntg-context
2021-08-22 22:21 ` Wolfgang Schuster via ntg-context
2021-08-23 6:19 ` Hans Hagen via ntg-context
2021-08-22 22:55 ` lmtx update Benjamin Buchmuller via ntg-context
1 sibling, 2 replies; 29+ messages in thread
From: Benjamin Buchmuller via ntg-context @ 2021-08-22 22:10 UTC (permalink / raw)
To: mailing list for ConTeXt users; +Cc: Benjamin Buchmuller
Hi,
Thanks for having had a look into the t-vim.
At least the document compiles fine (I get a PDF), although multiple complaints from the lua end when I use "$" or "#" in my source, for example
#!/usr/bin/bash
etc. culminating in
Sorry, but I'm not programmed to handle this case;
I'll just pretend that you didn''t ask for it.
If you're in the wrong mode, you might be able to
return to the right one by typing 'I}' or 'I$' or 'I\par'.
Seems as if LMTX tried to interpret something literally here …
Further, I get a lot of
fonts > beware: no fonts are loaded yet, using 'lm mono' in box
fonts > checking > char i (U+00069) in font '' with id 0: missing
fonts > checking > char n (U+0006E) in font '' with id 0: missing
warnings. Maybe some things need to be adjusted?
(Second mail with another error in LMTX follows.)
Cheers
Benjamin
> On Aug 20, 2021, at 12:00, ntg-context-request@ntg.nl wrote:
>
> Hi,
>
> Here are the highlights of todays update:
>
> - somewhat more compact tuc files, not for all documents, but it can accumulate; also less memory used then; i could bring down an extreme 2000 page 5 column doc tuc file down to 5% -- it was 70 MB; for the luametatex manual it reducec the tuc more than 30%; hard to tell if there will be an associated performance hit, but i'm sure thomas will complain if that's the case
>
> - more mp-tex-lua interfacing upgraded plus extra preliminary chapter for luametafun about extensions - for taco
>
> - a slightly more compact cache files for fonts with many (pseudo) ligatures; hopefully no side effects (nothing that can't be fixed fast if noted); quite probably no performance hit and maybe even some room for optimization (not done yet)
>
> - a split in the cache directory for luametatex so that we can more easilly experiment without interference (so, although the above works in mkiv it's not enabled there currently)
>
> - some minor things (also in the process of splitting the codebase)
>
> - no real changes in / additions to the luametatex binary (we're in cosmetics mode now)
>
> 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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update/t-vim (again)
2021-08-22 22:10 ` lmtx update/t-vim (again) Benjamin Buchmuller via ntg-context
@ 2021-08-22 22:21 ` Wolfgang Schuster via ntg-context
2021-08-23 6:19 ` Hans Hagen via ntg-context
1 sibling, 0 replies; 29+ messages in thread
From: Wolfgang Schuster via ntg-context @ 2021-08-22 22:21 UTC (permalink / raw)
To: mailing list for ConTeXt users; +Cc: Wolfgang Schuster
Benjamin Buchmuller via ntg-context schrieb am 23.08.2021 um 00:10:
> Hi,
>
> Thanks for having had a look into the t-vim.
>
> At least the document compiles fine (I get a PDF), although multiple complaints from the lua end when I use "$" or "#" in my source, for example
>
> #!/usr/bin/bash
>
> etc. culminating in
>
> Sorry, but I'm not programmed to handle this case;
> I'll just pretend that you didn''t ask for it.
> If you're in the wrong mode, you might be able to
> return to the right one by typing 'I}' or 'I$' or 'I\par'.
>
> Seems as if LMTX tried to interpret something literally here …
>
> Further, I get a lot of
>
> fonts > beware: no fonts are loaded yet, using 'lm mono' in box
> fonts > checking > char i (U+00069) in font '' with id 0: missing
> fonts > checking > char n (U+0006E) in font '' with id 0: missing
>
> warnings. Maybe some things need to be adjusted?
>
> (Second mail with another error in LMTX follows.)
Can you provide a minimal working (or in your case not working) example
for the problem.
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* lmtx update
[not found] <mailman.0.1629453601.23792.ntg-context@ntg.nl>
2021-08-22 22:10 ` lmtx update/t-vim (again) Benjamin Buchmuller via ntg-context
@ 2021-08-22 22:55 ` Benjamin Buchmuller via ntg-context
2021-08-23 6:21 ` Hans Hagen via ntg-context
1 sibling, 1 reply; 29+ messages in thread
From: Benjamin Buchmuller via ntg-context @ 2021-08-22 22:55 UTC (permalink / raw)
To: mailing list for ConTeXt users; +Cc: Benjamin Buchmuller
Hi,
Here is another thing which worked previously for me:
ConTeXt ver: 2021.07.30 00:57 LMTX fmt: 2021.8.8 int: english/english
Now:
ConTeXt ver: 2021.08.22 11:54 LMTX fmt: 2021.8.22 int: english/english
Error:
lua error:
registered function call [396]: ...eXt/tex/texmf-context/tex/context/base/mkxl/anch-pos.lmt:1286: attempt to call a nil value (upvalue 'texgetparstate')
stack traceback:
...eXt/tex/texmf-context/tex/context/base/mkxl/anch-pos.lmt:1286: in function <...eXt/tex/texmf-context/tex/context/base/mkxl/anch-pos.lmt:1262>
(...tail calls...)
129 \NC \unit{0.88 angstrom}
130 \NC \unit{2.02 angstrom}
131 \NC \unit{2.03 angstrom}
132 \NC \unit{1.90 angstrom}
133 \NC \unit{4.99 angstrom} % rmsd #1/a:14-61 & backbone to #5/a:103-150 & backbone
134 \NC \unit{1.88 angstrom}
135 \NC \unit{5.20 angstrom} % rmsd #1/a:46-55 & backbone to #5/a:135-144 & backbone
136 \NC \NR
137 \HL
138 \stoptabulate
The difficulty here is that when I copy the "faulty" part (my table) to another document (including all relevant defs etc.) it just works fine. So, I think it must have to do something with the placement of the float on the page.
Any hints what has changed?
Thanks!
Benjamin
> On Aug 20, 2021, at 12:00, ntg-context-request@ntg.nl wrote:
>
> lmtx update
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update/t-vim (again)
2021-08-22 22:10 ` lmtx update/t-vim (again) Benjamin Buchmuller via ntg-context
2021-08-22 22:21 ` Wolfgang Schuster via ntg-context
@ 2021-08-23 6:19 ` Hans Hagen via ntg-context
2021-08-23 10:32 ` Benjamin Buchmuller via ntg-context
1 sibling, 1 reply; 29+ messages in thread
From: Hans Hagen via ntg-context @ 2021-08-23 6:19 UTC (permalink / raw)
To: mailing list for ConTeXt users; +Cc: Hans Hagen, Benjamin Buchmuller
On 8/23/2021 12:10 AM, Benjamin Buchmuller via ntg-context wrote:
> Hi,
>
> Thanks for having had a look into the t-vim.
>
> At least the document compiles fine (I get a PDF), although multiple complaints from the lua end when I use "$" or "#" in my source, for example
>
> #!/usr/bin/bash
>
> etc. culminating in
>
> Sorry, but I'm not programmed to handle this case;
> I'll just pretend that you didn''t ask for it.
> If you're in the wrong mode, you might be able to
> return to the right one by typing 'I}' or 'I$' or 'I\par'.
>
> Seems as if LMTX tried to interpret something literally here …
>
> Further, I get a lot of
>
> fonts > beware: no fonts are loaded yet, using 'lm mono' in box
> fonts > checking > char i (U+00069) in font '' with id 0: missing
> fonts > checking > char n (U+0006E) in font '' with id 0: missing
>
> warnings. Maybe some things need to be adjusted?
THis normally means that you have someting before the \starttext that
gets typeset (here the word "in")
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update
2021-08-22 22:55 ` lmtx update Benjamin Buchmuller via ntg-context
@ 2021-08-23 6:21 ` Hans Hagen via ntg-context
0 siblings, 0 replies; 29+ messages in thread
From: Hans Hagen via ntg-context @ 2021-08-23 6:21 UTC (permalink / raw)
To: mailing list for ConTeXt users; +Cc: Hans Hagen, Benjamin Buchmuller
On 8/23/2021 12:55 AM, Benjamin Buchmuller via ntg-context wrote:
> Hi,
>
> Here is another thing which worked previously for me:
>
> ConTeXt ver: 2021.07.30 00:57 LMTX fmt: 2021.8.8 int: english/english
>
> Now:
>
> ConTeXt ver: 2021.08.22 11:54 LMTX fmt: 2021.8.22 int: english/english
>
> Error:
>
> lua error:
>
> registered function call [396]: ...eXt/tex/texmf-context/tex/context/base/mkxl/anch-pos.lmt:1286: attempt to call a nil value (upvalue 'texgetparstate')
> stack traceback:
> ...eXt/tex/texmf-context/tex/context/base/mkxl/anch-pos.lmt:1286: in function <...eXt/tex/texmf-context/tex/context/base/mkxl/anch-pos.lmt:1262>
> (...tail calls...)
>
> 129 \NC \unit{0.88 angstrom}
> 130 \NC \unit{2.02 angstrom}
> 131 \NC \unit{2.03 angstrom}
> 132 \NC \unit{1.90 angstrom}
> 133 \NC \unit{4.99 angstrom} % rmsd #1/a:14-61 & backbone to #5/a:103-150 & backbone
> 134 \NC \unit{1.88 angstrom}
> 135 \NC \unit{5.20 angstrom} % rmsd #1/a:46-55 & backbone to #5/a:135-144 & backbone
> 136 \NC \NR
> 137 \HL
> 138 \stoptabulate
>
> The difficulty here is that when I copy the "faulty" part (my table) to another document (including all relevant defs etc.) it just works fine. So, I think it must have to do something with the placement of the float on the page.
>
> Any hints what has changed?
your luametatex binary seems older than in the lmtx distribution .. what
platform?
-----------------------------------------------------------------
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update/t-vim (again)
2021-08-23 6:19 ` Hans Hagen via ntg-context
@ 2021-08-23 10:32 ` Benjamin Buchmuller via ntg-context
2021-08-23 17:42 ` Aditya Mahajan via ntg-context
0 siblings, 1 reply; 29+ messages in thread
From: Benjamin Buchmuller via ntg-context @ 2021-08-23 10:32 UTC (permalink / raw)
To: Hans Hagen; +Cc: Benjamin Buchmuller, mailing list for ConTeXt users
[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]
This is the setup I have been using, but I'm unsure if the problem could be related to the other problem I had. (Not scaled to a MWE, but short enough.) I figured the issue by removing some of the lines.
\usemodule[vim]
\definetextbackground[codebkg]
[
frame=on,
framecolor=black,
background=,
location=paragraph,
]
\definevimtyping[vimR]
[
syntax=r,
space=off,
lines=split,
numbering=yes,
numberstep=5,
alternative=pscolor,
margin=.5em,
style={\switchtobodyfont[type,small]\setupinterlinespace},
before={\blank[white,small]\startcodebkg}, % a bit of extra space
after={\stopcodebkg},
directory=vimout/, % note: you must create this folder yourself!
]
\starttext
\startvimR
#!/usr/bin/env R
included_aa <- list(
`6d1t` = 2:81,
`6cnq` = 146:225,
`6ccg` = 2:81,
`4lg7` = 76:167,
`3c2i` = 90:181) %>% enframe() %>% unnest(cols = "value") %>%
rename(protein = "name", aa_pos = "value") %>%
mutate(chain = "A") %>% mutate(include_aa = TRUE)
\stopvimR
\stoptext
So, the first "i", "n" etc. come from "include_aa" after I remove the shebang statement.
The lines with "#" and "$" (in other pieces not shown) cause the complaints.
I also realized that I get output for each vim block, but instead of a "vimout", I get a "pdf" (error) and a "log" (some attached) now.
Also, the blocks get recompiled with each run even if their content doesn't change which was the previous behavior.
[-- Attachment #2: xxx-temp-vimR-0-error.log --]
[-- Type: application/octet-stream, Size: 524 bytes --]
return {
["errortype"]=0,
["filename"]="vimout/mbd_scaffold-temp-vimR-0.tmp",
["lastcontext"]="\n<line 3.1> #\n !/usr/bin/env R",
["lastluaerror"]="",
["lasttexerror"]="You can't use 'parameter character #' in vertical mode",
["lasttexhelp"]="Sorry, but I'm not programmed to handle this case;\nI'll just pretend that you didn''t ask for it.\nIf you're in the wrong mode, you might be able to\nreturn to the right one by typing 'I}' or 'I$' or 'I\\par'.",
["linenumber"]=1,
["offset"]=10,
["skiplinenumber"]=0,
}
[-- Attachment #3: xxx-temp-vimR-0.log --]
[-- Type: application/octet-stream, Size: 1599 bytes --]
system >
system > ConTeXt ver: 2021.08.22 11:54 LMTX fmt: 2021.8.22 int: english/english
system >
system > 'cont-new.mkxl' loaded
open source > level 1, order 1, name '/Applications/ConTeXt/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > beware: some patches loaded from cont-new.mkiv
close source > level 1, order 1, name '/Applications/ConTeXt/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname 'vimout/mbd_scaffold-temp-vimR-0', input 'vimout/mbd_scaffold-temp-vimR-0.tmp', result 'vimout/mbd_scaffold-temp-vimR-0'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 1, order 2, name 'vimout/mbd_scaffold-temp-vimR-0.tmp'
tex error > tex error on line 1 in file vimout/mbd_scaffold-temp-vimR-0.tmp: You can't use 'parameter character #' in vertical mode
<line 3.1> #
!/usr/bin/env R
1 >> #!/usr/bin/env R
2 library(tidyverse)
3
4 read_csa <- function(file) {
5
6 readr::read_tsv(file) %>%
7 tidyr::pivot_longer(-1) %>%
8 magrittr::set_colnames(c("target", "buried_by", "value")) %>%
9 dplyr::mutate(
10 tar = stringr::str_extract(target, "^.+(?=/.+/)"),
11 tar_chain = stringr::str_extract(target, "(?<=/)[A-Z]+(?=/)"),
Sorry, but I'm not programmed to handle this case;
I'll just pretend that you didn''t ask for it.
If you're in the wrong mode, you might be able to
return to the right one by typing 'I}' or 'I$' or 'I\par'.
[-- Attachment #4: xxx-temp-vimR-1.log --]
[-- Type: application/octet-stream, Size: 13244 bytes --]
system >
system > ConTeXt ver: 2021.08.22 11:54 LMTX fmt: 2021.8.22 int: english/english
system >
system > 'cont-new.mkxl' loaded
open source > level 1, order 1, name '/Applications/ConTeXt/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > beware: some patches loaded from cont-new.mkiv
close source > level 1, order 1, name '/Applications/ConTeXt/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname 'vimout/mbd_scaffold-temp-vimR-1', input 'vimout/mbd_scaffold-temp-vimR-1.tmp', result 'vimout/mbd_scaffold-temp-vimR-1'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 1, order 2, name 'vimout/mbd_scaffold-temp-vimR-1.tmp'
close source > level 1, order 2, name 'vimout/mbd_scaffold-temp-vimR-1.tmp'
system > invalid \starttext ... \stoptext structure
fonts > beware: no fonts are loaded yet, using 'lm mono' in box
fonts > checking > char i (U+00069) in font '' with id 0: missing
fonts > checking > char n (U+0006E) in font '' with id 0: missing
fonts > checking > char c (U+00063) in font '' with id 0: missing
fonts > checking > char l (U+0006C) in font '' with id 0: missing
fonts > checking > char u (U+00075) in font '' with id 0: missing
fonts > checking > char d (U+00064) in font '' with id 0: missing
fonts > checking > char e (U+00065) in font '' with id 0: missing
fonts > checking > char _ (U+0005F) in font '' with id 0: missing
fonts > checking > char a (U+00061) in font '' with id 0: missing
fonts > checking > char < (U+0003C) in font '' with id 0: missing
fonts > checking > char - (U+0002D) in font '' with id 0: missing
fonts > checking > char s (U+00073) in font '' with id 0: missing
fonts > checking > char t (U+00074) in font '' with id 0: missing
fonts > checking > char ( (U+00028) in font '' with id 0: missing
fonts > checking > char ` (U+00060) in font '' with id 0: missing
fonts > checking > char 6 (U+00036) in font '' with id 0: missing
fonts > checking > char 1 (U+00031) in font '' with id 0: missing
fonts > checking > char = (U+0003D) in font '' with id 0: missing
fonts > checking > char 2 (U+00032) in font '' with id 0: missing
fonts > checking > char : (U+0003A) in font '' with id 0: missing
fonts > checking > char 8 (U+00038) in font '' with id 0: missing
fonts > checking > char , (U+0002C) in font '' with id 0: missing
fonts > checking > char q (U+00071) in font '' with id 0: missing
fonts > checking > char 4 (U+00034) in font '' with id 0: missing
fonts > checking > char 5 (U+00035) in font '' with id 0: missing
fonts > checking > char g (U+00067) in font '' with id 0: missing
fonts > checking > char 7 (U+00037) in font '' with id 0: missing
fonts > checking > char 3 (U+00033) in font '' with id 0: missing
fonts > checking > char 9 (U+00039) in font '' with id 0: missing
fonts > checking > char 0 (U+00030) in font '' with id 0: missing
fonts > checking > char ) (U+00029) in font '' with id 0: missing
fonts > checking > char r (U+00072) in font '' with id 0: missing
fonts > checking > char m (U+0006D) in font '' with id 0: missing
fonts > checking > char p (U+00070) in font '' with id 0: missing
fonts > checking > char o (U+0006F) in font '' with id 0: missing
fonts > checking > char " (U+00022) in font '' with id 0: missing
fonts > checking > char v (U+00076) in font '' with id 0: missing
fonts > checking > char h (U+00068) in font '' with id 0: missing
fonts > checking > char A (U+00041) in font '' with id 0: missing
backend > xmp > using file '/Applications/ConTeXt/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml'
pages > flushing realpage 1, userpage 1, subpage 1
system > start used files
system > text: mbd_scaffold-temp-vimR-1
system > stop used files
system > start used files
system > 1: filename=publ-imp-default.lua filetype=lua foundname=/Applications/ConTeXt/tex/texmf-context/tex/context/base/mkiv/publ-imp-default.lua fullname=/Applications/ConTeXt/tex/texmf-context/tex/context/base/mkiv/publ-imp-default.lua usedmethod=database
system > 2: filename=cont-new.mkxl filetype=tex foundname=/Applications/ConTeXt/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl fullname=/Applications/ConTeXt/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl usedmethod=database
system > 3: filename=lang-exc.lua filetype=lua foundname=/Applications/ConTeXt/tex/texmf-context/tex/context/base/mkiv/lang-exc.lua fullname=/Applications/ConTeXt/tex/texmf-context/tex/context/base/mkiv/lang-exc.lua usedmethod=database
system > 4: filename=lang-us.lua filetype=lua foundname=/Applications/ConTeXt/tex/texmf-context/tex/context/patterns/mkiv/lang-us.lua fullname=/Applications/ConTeXt/tex/texmf-context/tex/context/patterns/mkiv/lang-us.lua usedmethod=database
system > 5: filename=vimout/mbd_scaffold-temp-vimR-1.tmp format=tex foundname=vimout/mbd_scaffold-temp-vimR-1.tmp fullname=/Users/benjamin/Documents/university/1712-2103-PhD/thesis-PhD/_sync/02_thesis/publication-thesis_P-v2/maintexts/vimout/mbd_scaffold-temp-vimR-1.tmp usedmethod=direct
system > 6: filename=lmmono10-regular filetype=otf format=otf foundname=/Applications/ConTeXt/tex/texmf/fonts/opentype/public/lm/lmmono10-regular.otf fullname=/Applications/ConTeXt/tex/texmf/fonts/opentype/public/lm/lmmono10-regular.otf usedmethod=database
system > 7: filename=lpdf-pdx.xml filetype=tex foundname=/Applications/ConTeXt/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml fullname=/Applications/ConTeXt/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml usedmethod=database
system > stop used files
system > start commandline options
system > currentrun="1"
system > fulljobname="vimout/mbd_scaffold-temp-vimR-1.tmp"
system > input="vimout/mbd_scaffold-temp-vimR-1.tmp"
system > kindofrun="1"
system > maxnofruns="9"
system > texmfbinpath="/Applications/ConTeXt/tex/texmf-osx-64/bin"
system > stop commandline options
system > start commandline files
system > 1: vimout/mbd_scaffold-temp-vimR-1.tmp
system > stop commandline files
modules > start used modules
modules > stop used modules
system >
system > status after finishing run
system >
system > -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
system > string pool hash lookup node token buffer input file nest parameter save font language mark insert
system > -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
system > max 2097152 100000000 2097152 2097152 50000000 10000000 100000000 100000 2000 10000 100000 500000 100000 10000 10000 500
system > min 150000 10000000 150000 150000 1000000 1000000 1000000 10000 500 1000 20000 100000 250 250 50 10
system > set 500000 10000000 250000 250000 50000000 10000000 10000000 100000 2000 10000 100000 500000 100000 250 250 250
system > stp 100000 1000000 100000 100000 500000 250000 1000000 10000 250 1000 10000 10000 250 250 50 25
system >
system > mem 150000 840622 150000 1000000 1000000 1000000 10000 500 1000 20000 10000 46440 96 1200 240
system > all 3600000 840622 2400000 9000000 8000000 1000000 320000 16000 48000 80000 160000 46440 96 28800 5760
system >
system > ini 2141682 840331 0 44513 0 489954 0
system > ptr 44554 8606 44537 489941 0 0 0 0 0 0 1 0 0 7
system > top 44555 740037 131074 4574 490748 141 37 4 12 36 406 250 250 50 10
system > -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
system >
system > current input type : initial
system >
system > approximate memory : 27242854 (25 MB)
system >
system > expansion depth : min: 10000, max: 1000000, set: 10000, top: 7
system >
system > luabytecode registers : 997
system > luabytecode bytes : 15968 (0 MB)
system > luastate bytes now : 36129040 (34 MB)
system > luastate bytes max : 36590329 (34 MB)
system >
system > file callbacks : 63
system > saved callbacks : 422
system > direct callbacks : 2
system > function callbacks : 187
system > value callbacks : 1
system > message callbacks : 0
system > bytecode callbacks : 597
system >
system > mp instances : 0
system > mp estimated memory : 0 (0 MB)
system > mp file callbacks : 0
system > mp text callbacks : 0
system > mp script callbacks : 0
system > mp log callbacks : 0
system >
system > total callbacks : 1272
system > mp total callbacks : 0
system > backend callbacks : 0
system >
mkiv lua stats > used config file: selfautoparent:/texmf/web2c/texmfcnf.lua
mkiv lua stats > used cache path: /Applications/ConTeXt/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e
mkiv lua stats > resource resolver: loadtime 0.006 seconds, 0 scans with scantime 0.000 seconds, 0 shared scans, 7 found files, scanned paths: <none>
mkiv lua stats > stored bytecode data: 497 modules (0.255 sec), 100 tables (0.012 sec), 597 chunks (0.267 sec)
mkiv lua stats > traced context: maxstack: 1591, freed: 0, unreachable: 1591
mkiv lua stats > cleaned up reserved nodes: 69 nodes, 9 lists of 434
mkiv lua stats > node memory usage: 6 attribute, 3 attribute_list, 1 glue, 58 glue_spec, 3 kern, 2 penalty, 2 temp
mkiv lua stats > node list callback tasks: 9 unique task lists, 8 instances (re)created, 46 calls
mkiv lua stats > used backend: pdf (backend for directly generating pdf output)
mkiv lua stats > jobdata time: 0.001 seconds saving, 0.000 seconds loading
mkiv lua stats > callbacks: file: 63, saved: 422, direct: 2, function: 187, value: 1, message: 0, bytecode: 597, late 0, total: 1272 (1272 per page)
mkiv lua stats > randomizer: resumed with value 0.82560840936925
mkiv lua stats > loaded patterns: en::1, load time: 0.000
mkiv lua stats > loaded fonts: 1 files: lmmono10-regular.otf
mkiv lua stats > font engine: otf 3.119, afm 1.513, tfm 1.000, 1 instances, load time 0.010 seconds
mkiv lua stats > font embedding time: 0.001 seconds, 1 fonts
mkiv lua stats > result saved in file: vimout/mbd_scaffold-temp-vimR-1.pdf, compresslevel 1, objectcompresslevel 3
mkiv lua stats > positions: 4 collected, 0 deltas, 0 shared partials, 0 partial entries
mkiv lua stats > used platform: osx-64, type: unix, binary subtree: texmf-osx-64
mkiv lua stats > used engine: luametatex version: 2.0918, functionality level: 20210804, format id: 589, compiler: clang
mkiv lua stats > tex properties: 740037 hash slots used of 2097152, 44537 control sequences, approximate memory usage: 25 MB
mkiv lua stats > lua properties: engine: lua 5.4, used memory: 36 MB, ctx: 34 MB, max: 34 MB, symbol mask: utf (τεχ)
mkiv lua stats > runtime: 0.340 seconds, 1 processed pages, 1 shipped pages, 2.939 pages/second
[-- Attachment #5: Type: text/plain, Size: 1473 bytes --]
> On Aug 23, 2021, at 08:19, Hans Hagen <j.hagen@xs4all.nl> wrote:
>
> On 8/23/2021 12:10 AM, Benjamin Buchmuller via ntg-context wrote:
>> Hi,
>> Thanks for having had a look into the t-vim.
>> At least the document compiles fine (I get a PDF), although multiple complaints from the lua end when I use "$" or "#" in my source, for example
>> #!/usr/bin/bash
>> etc. culminating in
>> Sorry, but I'm not programmed to handle this case;
>> I'll just pretend that you didn''t ask for it.
>> If you're in the wrong mode, you might be able to
>> return to the right one by typing 'I}' or 'I$' or 'I\par'.
>> Seems as if LMTX tried to interpret something literally here …
>> Further, I get a lot of
>> fonts > beware: no fonts are loaded yet, using 'lm mono' in box
>> fonts > checking > char i (U+00069) in font '' with id 0: missing
>> fonts > checking > char n (U+0006E) in font '' with id 0: missing
>> warnings. Maybe some things need to be adjusted?
> THis normally means that you have someting before the \starttext that gets typeset (here the word "in")
>
> 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
> -----------------------------------------------------------------
[-- Attachment #6: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update/t-vim (again)
2021-08-23 10:32 ` Benjamin Buchmuller via ntg-context
@ 2021-08-23 17:42 ` Aditya Mahajan via ntg-context
2021-08-23 17:45 ` Hans Hagen via ntg-context
2021-08-25 2:45 ` Aditya Mahajan via ntg-context
0 siblings, 2 replies; 29+ messages in thread
From: Aditya Mahajan via ntg-context @ 2021-08-23 17:42 UTC (permalink / raw)
To: Benjamin Buchmuller via ntg-context; +Cc: Aditya Mahajan, Benjamin Buchmuller
On Mon, 23 Aug 2021, Benjamin Buchmuller via ntg-context wrote:
> This is the setup I have been using, but I'm unsure if the problem could be related to the other problem I had. (Not scaled to a MWE, but short enough.) I figured the issue by removing some of the lines.
I get the same error. Most likely due to some grouping issue because there is also this:
system > invalid \starttext ... \stoptext structure
I'll look into it.
Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update/t-vim (again)
2021-08-23 17:42 ` Aditya Mahajan via ntg-context
@ 2021-08-23 17:45 ` Hans Hagen via ntg-context
2021-08-25 2:45 ` Aditya Mahajan via ntg-context
1 sibling, 0 replies; 29+ messages in thread
From: Hans Hagen via ntg-context @ 2021-08-23 17:45 UTC (permalink / raw)
To: Aditya Mahajan, Benjamin Buchmuller via ntg-context
Cc: Hans Hagen, Benjamin Buchmuller
On 8/23/2021 7:42 PM, Aditya Mahajan wrote:
> On Mon, 23 Aug 2021, Benjamin Buchmuller via ntg-context wrote:
>
>> This is the setup I have been using, but I'm unsure if the problem could be related to the other problem I had. (Not scaled to a MWE, but short enough.) I figured the issue by removing some of the lines.
>
> I get the same error. Most likely due to some grouping issue because there is also this:
>
> system > invalid \starttext ... \stoptext structure
>
> I'll look into it.
Hopefully I didn't mess up something.
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update/t-vim (again)
2021-08-23 17:42 ` Aditya Mahajan via ntg-context
2021-08-23 17:45 ` Hans Hagen via ntg-context
@ 2021-08-25 2:45 ` Aditya Mahajan via ntg-context
1 sibling, 0 replies; 29+ messages in thread
From: Aditya Mahajan via ntg-context @ 2021-08-25 2:45 UTC (permalink / raw)
To: Aditya Mahajan via ntg-context; +Cc: Aditya Mahajan, Benjamin Buchmuller
On Mon, 23 Aug 2021, Aditya Mahajan via ntg-context wrote:
> On Mon, 23 Aug 2021, Benjamin Buchmuller via ntg-context wrote:
>
> > This is the setup I have been using, but I'm unsure if the problem could be related to the other problem I had. (Not scaled to a MWE, but short enough.) I figured the issue by removing some of the lines.
>
> I get the same error. Most likely due to some grouping issue because there is also this:
>
> system > invalid \starttext ... \stoptext structure
>
> I'll look into it.
The error was due to the change in job.files.run macro. I have adapted the t-filter module to use the new interface. So, the error should go away if you update your installed modules.
Thanks for the bug report.
Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* lmtx update
@ 2023-02-06 17:21 Hans Hagen via ntg-context
0 siblings, 0 replies; 29+ messages in thread
From: Hans Hagen via ntg-context @ 2023-02-06 17:21 UTC (permalink / raw)
To: mailing list for ConTeXt users; +Cc: Hans Hagen
Hi,
We were considering to drop the virtual math fonts mechanism (which has
served its purpose in the transition in the very early days of luatex
but became obsolete as math fonts evolved) but in the end we were forced
keep this feature and even upgrade it because we liked iwona, kurier and
anwykwa math too much. A typical case where one needs a week for
reviewing, supporting, discussing, testing a few fonts, so let's hope it
wi;l be used. Iwona and Kurier are nice sansish fonts and antykwa has a
rather distinctive look and feel.
The current variant works okay for most of math (in most weights of the
fonts) but then, these fonts are not used for complex math or math
using obscure symbols anyway.
It can also serve as a test case for somewhat ancient fonts but it is
configured in the modern way we like more (as we might completely drop
old code paths some day anyway).
And so, this update is dedicated to Janusz Nowacki, a Polish font
friend, who passed away some time ago.
% \setupbodyfont[iwona]
% \setupbodyfont[kurier]
% \setupbodyfont[antykwa]
Hans & Mikael
-----------------------------------------------------------------
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 / 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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update
2021-08-19 20:07 ` Aditya Mahajan via ntg-context
@ 2021-08-20 5:52 ` Hans Hagen via ntg-context
0 siblings, 0 replies; 29+ messages in thread
From: Hans Hagen via ntg-context @ 2021-08-20 5:52 UTC (permalink / raw)
To: Aditya Mahajan via ntg-context; +Cc: Hans Hagen
On 8/19/2021 10:07 PM, Aditya Mahajan via ntg-context wrote:
> On Thu, 19 Aug 2021, Hans Hagen via ntg-context wrote:
>
>> Hi,
>>
>> Here are the highlights of todays update:
>>
>> - somewhat more compact tuc files, not for all documents, but it can
>> accumulate; also less memory used then; i could bring down an extreme
>> 2000 page 5 column doc tuc file down to 5% -- it was 70 MB; for the
>> luametatex manual it reducec the tuc more than 30%; hard to tell if
>> there will be an associated performance hit, but i'm sure thomas will
>> complain if that's the case
>
> I never realized that tuc files can grow so big. For big documents, would it make sense to simply read and write zipped tuc files?
normally they are not that large but when you enable for instance
mechanisms that need positioning they can grow large .. zipping makes
for less bytes but still large files and the overhead for serialization
stays
(to some extend trying to make these things small is like compression
but in a different way .. could be a nice topic for a ctx meeting)
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update
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
0 siblings, 1 reply; 29+ messages in thread
From: Aditya Mahajan via ntg-context @ 2021-08-19 20:07 UTC (permalink / raw)
To: Hans Hagen via ntg-context; +Cc: Aditya Mahajan
On Thu, 19 Aug 2021, Hans Hagen via ntg-context wrote:
> Hi,
>
> Here are the highlights of todays update:
>
> - somewhat more compact tuc files, not for all documents, but it can
> accumulate; also less memory used then; i could bring down an extreme
> 2000 page 5 column doc tuc file down to 5% -- it was 70 MB; for the
> luametatex manual it reducec the tuc more than 30%; hard to tell if
> there will be an associated performance hit, but i'm sure thomas will
> complain if that's the case
I never realized that tuc files can grow so big. For big documents, would it make sense to simply read and write zipped tuc files?
Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* lmtx update
@ 2021-08-19 17:57 Hans Hagen via ntg-context
2021-08-19 20:07 ` Aditya Mahajan via ntg-context
0 siblings, 1 reply; 29+ messages in thread
From: Hans Hagen via ntg-context @ 2021-08-19 17:57 UTC (permalink / raw)
To: mailing list for ConTeXt users; +Cc: Hans Hagen
Hi,
Here are the highlights of todays update:
- somewhat more compact tuc files, not for all documents, but it can
accumulate; also less memory used then; i could bring down an extreme
2000 page 5 column doc tuc file down to 5% -- it was 70 MB; for the
luametatex manual it reducec the tuc more than 30%; hard to tell if
there will be an associated performance hit, but i'm sure thomas will
complain if that's the case
- more mp-tex-lua interfacing upgraded plus extra preliminary chapter
for luametafun about extensions - for taco
- a slightly more compact cache files for fonts with many (pseudo)
ligatures; hopefully no side effects (nothing that can't be fixed fast
if noted); quite probably no performance hit and maybe even some room
for optimization (not done yet)
- a split in the cache directory for luametatex so that we can more
easilly experiment without interference (so, although the above works in
mkiv it's not enabled there currently)
- some minor things (also in the process of splitting the codebase)
- no real changes in / additions to the luametatex binary (we're in
cosmetics mode now)
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update
2020-09-17 10:50 ` Eduardo Bohoyo
@ 2020-09-17 11:11 ` Eduardo Bohoyo
0 siblings, 0 replies; 29+ messages in thread
From: Eduardo Bohoyo @ 2020-09-17 11:11 UTC (permalink / raw)
To: ntg-context,
wolfgang.schuster.lists@gmail.com >> Wolfgang Schuster
El 17/9/20 a las 12:50, Eduardo Bohoyo escribió:
>
> El 17/9/20 a las 12:35, Wolfgang Schuster escribió:
>> Eduardo Bohoyo schrieb am 17.09.2020 um 10:14:
>>> Thank you for this illustrative example, Wolfgang.
>>>
>>> So, what \forgetparagraphfreezing does is to reverse the order that
>>> lmtx currently imposes by default, right? In other words,
>>> \forgetparagraphfreezing, recovers the default behaviour of MkIV.
>>>
>>> So, I suspect that this will not change; if we want to apply
>>> Lettrine to a paragraph, from now on we must wrap it up with
>>> \forgetparagraphfreezing and \setparagraphfreezing.
>>>
>>> Please correct me if I'm wrong.
>>
>> LMTX removes some restrictions for settings which are applies to
>> paragraphs, e.g. the following example works now without problems
>> with LMTX while LuaTeX needs the \dontleavehmode at the begin of the
>> paragraph
>>
>> \starttext
>>
>> \placefigure[left]{none}{\framed[width=2cm,height=2cm]{}}
>> %\dontleavehmode
>> {\bf Tufte: }\input tufte
>>
>> \stoptext
>>
>> To avoid side effects from these changes LMTX freezes a few settings
>> at the begin of the paragraph. In some cases commands or settings
>> have to be adapted to these changes and the lettrine module is one of
>> them.
>>
>> The changes itself to the commands have to be made in the modules
>> etc. itself and not in the documents, below is a minimal example how
>> the lettrine module has to be changed to get indentation for the
>> initial back.
>>
>> \starttext
>>
>> \hsize 10cm
>>
>> \noindent
>> \parshape 3 1cm 9cm 1.5cm 8.5cm 0cm 10cm
>> \input weisman
>>
>> \blank
>>
>> \begingroup
>> \noindent
>> \parshape 3 1cm 9cm 1.5cm 8.5cm 0cm 10cm
>> \updateparagraphshapes
>> \endgroup
>> \input weisman
>>
>> \stoptext
>>
>> BTW: ConTeXt already provides a command to place initials as part of
>> the core but it lacks a few features of the lettrine module.
>>
>> Wolfgang
>>
>
> OK, I get it.
>
> Oh, and yes, I knew about the \setupinitial command. Thanks for
> pointing that out.
Sorry, Wolfgag,
I forgot to sign my reply.
Eduardo
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update
2020-09-17 10:35 ` Wolfgang Schuster
@ 2020-09-17 10:50 ` Eduardo Bohoyo
2020-09-17 11:11 ` Eduardo Bohoyo
0 siblings, 1 reply; 29+ messages in thread
From: Eduardo Bohoyo @ 2020-09-17 10:50 UTC (permalink / raw)
To: ntg-context,
wolfgang.schuster.lists@gmail.com >> Wolfgang Schuster
El 17/9/20 a las 12:35, Wolfgang Schuster escribió:
> Eduardo Bohoyo schrieb am 17.09.2020 um 10:14:
>> Thank you for this illustrative example, Wolfgang.
>>
>> So, what \forgetparagraphfreezing does is to reverse the order that
>> lmtx currently imposes by default, right? In other words,
>> \forgetparagraphfreezing, recovers the default behaviour of MkIV.
>>
>> So, I suspect that this will not change; if we want to apply Lettrine
>> to a paragraph, from now on we must wrap it up with
>> \forgetparagraphfreezing and \setparagraphfreezing.
>>
>> Please correct me if I'm wrong.
>
> LMTX removes some restrictions for settings which are applies to
> paragraphs, e.g. the following example works now without problems with
> LMTX while LuaTeX needs the \dontleavehmode at the begin of the paragraph
>
> \starttext
>
> \placefigure[left]{none}{\framed[width=2cm,height=2cm]{}}
> %\dontleavehmode
> {\bf Tufte: }\input tufte
>
> \stoptext
>
> To avoid side effects from these changes LMTX freezes a few settings
> at the begin of the paragraph. In some cases commands or settings have
> to be adapted to these changes and the lettrine module is one of them.
>
> The changes itself to the commands have to be made in the modules etc.
> itself and not in the documents, below is a minimal example how the
> lettrine module has to be changed to get indentation for the initial
> back.
>
> \starttext
>
> \hsize 10cm
>
> \noindent
> \parshape 3 1cm 9cm 1.5cm 8.5cm 0cm 10cm
> \input weisman
>
> \blank
>
> \begingroup
> \noindent
> \parshape 3 1cm 9cm 1.5cm 8.5cm 0cm 10cm
> \updateparagraphshapes
> \endgroup
> \input weisman
>
> \stoptext
>
> BTW: ConTeXt already provides a command to place initials as part of
> the core but it lacks a few features of the lettrine module.
>
> Wolfgang
>
OK, I get it.
Oh, and yes, I knew about the \setupinitial command. Thanks for pointing
that out.
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update
2020-09-17 8:14 ` Eduardo Bohoyo
@ 2020-09-17 10:35 ` Wolfgang Schuster
2020-09-17 10:50 ` Eduardo Bohoyo
0 siblings, 1 reply; 29+ messages in thread
From: Wolfgang Schuster @ 2020-09-17 10:35 UTC (permalink / raw)
To: Eduardo Bohoyo; +Cc: ntg-context
Eduardo Bohoyo schrieb am 17.09.2020 um 10:14:
> Thank you for this illustrative example, Wolfgang.
>
> So, what \forgetparagraphfreezing does is to reverse the order that
> lmtx currently imposes by default, right? In other words,
> \forgetparagraphfreezing, recovers the default behaviour of MkIV.
>
> So, I suspect that this will not change; if we want to apply Lettrine
> to a paragraph, from now on we must wrap it up with
> \forgetparagraphfreezing and \setparagraphfreezing.
>
> Please correct me if I'm wrong.
LMTX removes some restrictions for settings which are applies to
paragraphs, e.g. the following example works now without problems with
LMTX while LuaTeX needs the \dontleavehmode at the begin of the paragraph
\starttext
\placefigure[left]{none}{\framed[width=2cm,height=2cm]{}}
%\dontleavehmode
{\bf Tufte: }\input tufte
\stoptext
To avoid side effects from these changes LMTX freezes a few settings at
the begin of the paragraph. In some cases commands or settings have to
be adapted to these changes and the lettrine module is one of them.
The changes itself to the commands have to be made in the modules etc.
itself and not in the documents, below is a minimal example how the
lettrine module has to be changed to get indentation for the initial back.
\starttext
\hsize 10cm
\noindent
\parshape 3 1cm 9cm 1.5cm 8.5cm 0cm 10cm
\input weisman
\blank
\begingroup
\noindent
\parshape 3 1cm 9cm 1.5cm 8.5cm 0cm 10cm
\updateparagraphshapes
\endgroup
\input weisman
\stoptext
BTW: ConTeXt already provides a command to place initials as part of the
core but it lacks a few features of the lettrine module.
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update
[not found] ` <6f2953c3-4b09-e824-da78-46347ef5f4af@disroot.org>
@ 2020-09-17 8:14 ` Eduardo Bohoyo
2020-09-17 10:35 ` Wolfgang Schuster
0 siblings, 1 reply; 29+ messages in thread
From: Eduardo Bohoyo @ 2020-09-17 8:14 UTC (permalink / raw)
To: Wolfgang Schuster, ntg-context
El 17/9/20 a las 1:07, ebohoyod escribió:
>
> El 16/9/20 a las 18:23, Wolfgang Schuster escribió:
>> ebohoyod schrieb am 16.09.2020 um 17:52:
>>> Hi,
>>>
>>> It seems that the Lettrine module is one of those affected:
>>>
>>> https://tex.stackexchange.com/questions/562534/does-context-fail-in-the-lmtx-environment-with-the-lettrine-module?noredirect=1#comment1418902_562534
>>>
>>>
>>> But, honestly, first, I don't know what means "/Of course it might
>>> have other side effects once in lmtx we everywhere expect freezing
>>> to be enabled./"
>>> I suppose that, in order not to be a nuisance (and not to digress
>>> into this real subject of interest), a short answer would be enough
>>> to put me on track to investigate it.
>>>
>>> On the other hand, I suppose the best practice, from what I have
>>> just read, would be not to use \forgetparagraphfreezing globaly, but
>>> \forgetparagraphfreezing and \setparagraphfreezing at the beginning
>>> and end of the first paragraph respectively of each chapter. Would
>>> this be the least harmful way? That is, wrapping it up to avoid this
>>> provisional failure of the Lettrine with LMTX module, but at the
>>> same time to avoid affecting that default freezing proposal in the
>>> rest of the document, right?
>>>
>>> By the way, and just out of curiosity, how does the recommended
>>> provisional command work? Would it be something like this in the
>>> preamble?:
>>>
>>> \definingparagraphs
>>> firstparagraph][n=1]
>>> \setupparagraphs [firstparagraph][1][align={hanging}]
>>>
>>> And then this arrangement in the \input files?:
>>>
>>> \startfirstparagraph
>>> \lettrine{B}{lah} blah, blah, blah...
>>> \stopfirstparagraph
>>> \blank [overlay] \strut
>>>
>>> I know it's a dirty, inelegant solution, but I can't think of a
>>> better one at the moment.
>>
>> Below is a minimal example which doesn't rely on the module,
>> the problem is caused by the order of the \noindent and \parshape
>> command.
>>
>> When a paragraph starts before the \parshape values are set
>> the arguments are ignored because the values are already frozen
>> at this moment, when you set the values before the paragraphs
>> starts ConTeXt applies them.
>>
>> \starttext
>>
>> \hsize 10cm
>>
>> % lettrine module, \noindent before \parshape
>>
>> \noindent
>> \parshape 3 1cm 9cm 1.5cm 8.5cm 0cm 10cm
>> \input weisman
>>
>> \blank
>>
>> % working order, \parshape before \noindent
>>
>> \parshape 3 1cm 9cm 1.5cm 8.5cm 0cm 10cm
>> \noindent
>> \input weisman
>>
>> \stoptext
>>
>> Wolfgang
>
Thank you for this illustrative example, Wolfgang.
So, what \forgetparagraphfreezing does is to reverse the order that lmtx
currently imposes by default, right? In other words,
\forgetparagraphfreezing, recovers the default behaviour of MkIV.
So, I suspect that this will not change; if we want to apply Lettrine to
a paragraph, from now on we must wrap it up with
\forgetparagraphfreezing and \setparagraphfreezing.
Please correct me if I'm wrong.
Eduardo.
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update
2020-09-16 15:52 ebohoyod
@ 2020-09-16 16:23 ` Wolfgang Schuster
[not found] ` <6f2953c3-4b09-e824-da78-46347ef5f4af@disroot.org>
0 siblings, 1 reply; 29+ messages in thread
From: Wolfgang Schuster @ 2020-09-16 16:23 UTC (permalink / raw)
To: mailing list for ConTeXt users; +Cc: Taco Hoekwater, ebohoyod
ebohoyod schrieb am 16.09.2020 um 17:52:
> Hi,
>
> It seems that the Lettrine module is one of those affected:
>
> https://tex.stackexchange.com/questions/562534/does-context-fail-in-the-lmtx-environment-with-the-lettrine-module?noredirect=1#comment1418902_562534
>
>
> But, honestly, first, I don't know what means "/Of course it might have
> other side effects once in lmtx we everywhere expect freezing to be
> enabled./"
> I suppose that, in order not to be a nuisance (and not to digress into
> this real subject of interest), a short answer would be enough to put me
> on track to investigate it.
>
> On the other hand, I suppose the best practice, from what I have just
> read, would be not to use \forgetparagraphfreezing globaly, but
> \forgetparagraphfreezing and \setparagraphfreezing at the beginning and
> end of the first paragraph respectively of each chapter. Would this be
> the least harmful way? That is, wrapping it up to avoid this provisional
> failure of the Lettrine with LMTX module, but at the same time to avoid
> affecting that default freezing proposal in the rest of the document,
> right?
>
> By the way, and just out of curiosity, how does the recommended
> provisional command work? Would it be something like this in the preamble?:
>
> \definingparagraphs
> firstparagraph][n=1]
> \setupparagraphs [firstparagraph][1][align={hanging}]
>
> And then this arrangement in the \input files?:
>
> \startfirstparagraph
> \lettrine{B}{lah} blah, blah, blah...
> \stopfirstparagraph
> \blank [overlay] \strut
>
> I know it's a dirty, inelegant solution, but I can't think of a better
> one at the moment.
Below is a minimal example which doesn't rely on the module,
the problem is caused by the order of the \noindent and \parshape
command.
When a paragraph starts before the \parshape values are set
the arguments are ignored because the values are already frozen
at this moment, when you set the values before the paragraphs
starts ConTeXt applies them.
\starttext
\hsize 10cm
% lettrine module, \noindent before \parshape
\noindent
\parshape 3 1cm 9cm 1.5cm 8.5cm 0cm 10cm
\input weisman
\blank
% working order, \parshape before \noindent
\parshape 3 1cm 9cm 1.5cm 8.5cm 0cm 10cm
\noindent
\input weisman
\stoptext
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* lmtx update
@ 2020-09-16 15:52 ebohoyod
2020-09-16 16:23 ` Wolfgang Schuster
0 siblings, 1 reply; 29+ messages in thread
From: ebohoyod @ 2020-09-16 15:52 UTC (permalink / raw)
To: ntg-context
[-- Attachment #1.1: Type: text/plain, Size: 1556 bytes --]
Hi,
It seems that the Lettrine module is one of those affected:
https://tex.stackexchange.com/questions/562534/does-context-fail-in-the-lmtx-environment-with-the-lettrine-module?noredirect=1#comment1418902_562534
But, honestly, first, I don't know what means "/Of course it might have
other side effects once in lmtx we everywhere expect freezing to be
enabled./"
I suppose that, in order not to be a nuisance (and not to digress into
this real subject of interest), a short answer would be enough to put me
on track to investigate it.
On the other hand, I suppose the best practice, from what I have just
read, would be not to use \forgetparagraphfreezing globaly, but
\forgetparagraphfreezing and \setparagraphfreezing at the beginning and
end of the first paragraph respectively of each chapter. Would this be
the least harmful way? That is, wrapping it up to avoid this provisional
failure of the Lettrine with LMTX module, but at the same time to avoid
affecting that default freezing proposal in the rest of the document,
right?
By the way, and just out of curiosity, how does the recommended
provisional command work? Would it be something like this in the preamble?:
\definingparagraphs
firstparagraph][n=1]
\setupparagraphs [firstparagraph][1][align={hanging}]
And then this arrangement in the \input files?:
\startfirstparagraph
\lettrine{B}{lah} blah, blah, blah...
\stopfirstparagraph
\blank [overlay] \strut
I know it's a dirty, inelegant solution, but I can't think of a better
one at the moment.
[-- Attachment #1.2: Type: text/html, Size: 2460 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update
2020-07-31 8:32 Hans Hagen
` (2 preceding siblings ...)
2020-08-02 3:30 ` Aditya Mahajan
@ 2020-08-03 17:37 ` Pablo Rodriguez
3 siblings, 0 replies; 29+ messages in thread
From: Pablo Rodriguez @ 2020-08-03 17:37 UTC (permalink / raw)
To: ntg-context
On 7/31/20 10:32 AM, Hans Hagen 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.
Hi Hans,
many thanks for your explanation.
I wonder whether the new improvements could prevent body text running
into the footnotes (as some of us have already reported).
> [...]
> No one ever requested it so see it an a quick and dirty example but
> don't hesitate to ask for more anyway (we like an occasional challenge).
If you are open for suggestions, I would ask for a footnotes that behave
as a page index, such as in:
\setuplanguage[en][patterns={en,agr}]
\setuppapersize[A6]
\setupbodyfont[dejavu]
\definenote[dict]
\setupnote[dict][n=2,rule=off,
split=strict, inbetween=\hskip1.5em]
\setupnotation[dict][number=no,
style={\tfx\setupinterlinespace[line=2.5ex]}]
\starttext
Πρῶτον δεῖ θέσθαι τί ὄνομα\dict{ὄνομα,
-ατος, τό: noun} καὶ τί ῥῆμα\dict{ῥῆμα, -ατος, τό: verb},
ἔπειτα τί ἐστιν
ἀπόφασις\dict{ἀπόφασις, -εως, ἡ: negation}
καὶ κατάφασις\dict{κατάφασις, εως, ἡ:
affirmation} καὶ ἀπόφανσις\dict{ἀπόφανσις,
-εως, ἡ: statement} καὶ λόγος.
\stoptext
What I need there is that these notes are alphabetically sorted, such as
in a standard register.
As I proposed that (years ago), you told me it was too complex. I wonder
whether this would be easier with the current developments.
Many thanks for your improvements to ConTeXt,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update
2020-07-31 8:32 Hans Hagen
2020-07-31 8:40 ` Taco Hoekwater
2020-08-01 13:20 ` Otared Kavian
@ 2020-08-02 3:30 ` Aditya Mahajan
2020-08-03 17:37 ` Pablo Rodriguez
3 siblings, 0 replies; 29+ messages in thread
From: Aditya Mahajan @ 2020-08-02 3:30 UTC (permalink / raw)
To: mailing list for ConTeXt users
On Fri, 31 Jul 2020, Hans Hagen wrote:
Thanks for the update.
> Other work in progress is: better columns in itemize, esp proper
> footnote support (not that I ever need that but I know users do so ...),
> experiments work ok, but I need to check spacing. In general, footnotes
> (will) behave a bit better, especially those used nested in other
> mechanisms. A side effect of more control is that we can do other tricks
> too and we're playing with it (kind of fun).
Does this mean we can get two-column footnotes in two-column documents?
Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update
2020-08-01 16:41 ` Henning Hraban Ramm
@ 2020-08-01 16:57 ` Otared Kavian
0 siblings, 0 replies; 29+ messages in thread
From: Otared Kavian @ 2020-08-01 16:57 UTC (permalink / raw)
To: mailing list for ConTeXt users
Hi Hraban,
Thank you for reminding me of the solution cooked up by Wolfgang for you a few years ago. That solution works fine when the notes are short enough, but in some cases the notes in the margin bump into each other (indeed it is not a good habit to have long notes, but in some cases one cannot avoid them).
Best regards: Otared
> On 1 Aug 2020, at 18:41, Henning Hraban Ramm <texml@fiee.net> wrote:
>
>
>> Am 01.08.2020 um 15:20 schrieb Otared Kavian <otared@gmail.com>:
>>
>> Regarding footnotes, would it be possible to have a built-in support for writing the footnotes in the margin? (For instance, assuming that the layout is such that for instance the right margin takes 1/3 of the page width, then the footnotes would occupy the right margin, beginning at the top).
>
> I wanted to have footnotes in the margin, possibly starting in the same line as the marker.
>
> Wolfgang came up with this:
> https://wiki.contextgarden.net/Footnotes#..._but_not_at_the_bottom
>
> (Not related to LMTX.)
>
> Hraban
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update
2020-08-01 13:20 ` Otared Kavian
2020-08-01 14:17 ` Hans Hagen
@ 2020-08-01 16:41 ` Henning Hraban Ramm
2020-08-01 16:57 ` Otared Kavian
1 sibling, 1 reply; 29+ messages in thread
From: Henning Hraban Ramm @ 2020-08-01 16:41 UTC (permalink / raw)
To: mailing list for ConTeXt users
> Am 01.08.2020 um 15:20 schrieb Otared Kavian <otared@gmail.com>:
>
> Regarding footnotes, would it be possible to have a built-in support for writing the footnotes in the margin? (For instance, assuming that the layout is such that for instance the right margin takes 1/3 of the page width, then the footnotes would occupy the right margin, beginning at the top).
I wanted to have footnotes in the margin, possibly starting in the same line as the marker.
Wolfgang came up with this:
https://wiki.contextgarden.net/Footnotes#..._but_not_at_the_bottom
(Not related to LMTX.)
Hraban
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update
2020-08-01 14:17 ` Hans Hagen
@ 2020-08-01 16:20 ` Otared Kavian
0 siblings, 0 replies; 29+ messages in thread
From: Otared Kavian @ 2020-08-01 16:20 UTC (permalink / raw)
To: mailing list for ConTeXt users
> On 1 Aug 2020, at 16:17, Hans Hagen <j.hagen@xs4all.nl> wrote:
>
> On 8/1/2020 3:20 PM, Otared Kavian wrote:
>>> On 31 Jul 2020, at 10:32, Hans Hagen <j.hagen@xs4all.nl> wrote:
>>>
>>> […]
>>>
>>> Other work in progress is: better columns in itemize, esp proper footnote support (not that I ever need that but I know users do so ...), experiments work ok, but I need to check spacing. In general, footnotes (will) behave a bit better, especially those used nested in other mechanisms. A side effect of more control is that we can do other tricks too and we're playing with it (kind of fun).
>> Hi Hans,
>> Thanks for your explanations.
>> Regarding footnotes, would it be possible to have a built-in support for writing the footnotes in the margin? (For instance, assuming that the layout is such that for instance the right margin takes 1/3 of the page width, then the footnotes would occupy the right margin, beginning at the top).
> It depends on what you want. This works ok:
> […]
Hi Hans,
That's great! Thanks a lot!
I have two questions in order to adapt what you sent to my case.
I played a bit with your second solution, as in:
%%%%%%% begin sidenote-Hans.tex
\showframe
\setupinteraction[state=start]
\setuplayout
[cutspace=7cm,
width=middle,
margin=5cm,
margindistance=7mm]
\setuptexttexts
[margin]
[] [{\directsetup{notabene}}]
\newbox\MyNoteOverflow
\setupnotation[endnote]
[interaction=yes,
after={\blank[big]}]
\startsetups notabene
\setbox\scratchbox\vbox
\bgroup
\setupalign[tolerant]
\ifvoid\MyNoteOverflow
\else
\unvbox\MyNoteOverflow
\fi
\placenotes[endnote][before=,after=]
\egroup
\scratchdimen\dimexpr\textheight-.5\lineheight\relax
\ifdim\ht\scratchbox>\scratchdimen
\global\setbox\MyNoteOverflow\box\scratchbox
\setbox\scratchbox\vsplit \MyNoteOverflow to \scratchdimen
\fi
\vbox
\bgroup
\topskipcorrection
\unvbox\scratchbox
\vfilll
\egroup
\stopsetups
\startsetups notaflush
\doloop {
\page
\ifvoid\MyNoteOverflow
\exitloop
\else
\null \page
\fi
}
\stopsetups
\starttext
\dorecurse{10}{
test \endnote{\input ward }\input tufte.tex \par
test \endnote{This is a note about Ward, who says: \par \input ward.tex} \input ward.tex \par
test \endnote{This is a note about Donald Knuth.} \input knuth.tex \par
}
This is a last note. \endnote{This last note is here to see what happens in the next page\dots\par \input knuth.tex}
\par \input knuth.tex
%\setups{notaflush}
\stoptext
%%%%%%% end sidenote-Hans.tex
The first question is why did you define a setups called notaflush, and why your example works fine without using it ?
The second question is: the side notes are vertically centered in the margin (one can see this when the notes do not cover all the margin), which is fine for me. But, out of curiosity, what can be changed in the setups notabene in order to have the notes to begin at the top of the margin ?
(When a note runs into the next page, as in the last note, then it would be nicer to begin on top of the margin).
Thanks again: Otared K.
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update
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
1 sibling, 1 reply; 29+ messages in thread
From: Hans Hagen @ 2020-08-01 14:17 UTC (permalink / raw)
To: mailing list for ConTeXt users, Otared Kavian
On 8/1/2020 3:20 PM, Otared Kavian wrote:
>> On 31 Jul 2020, at 10:32, Hans Hagen <j.hagen@xs4all.nl> wrote:
>>
>> […]
>>
>> Other work in progress is: better columns in itemize, esp proper footnote support (not that I ever need that but I know users do so ...), experiments work ok, but I need to check spacing. In general, footnotes (will) behave a bit better, especially those used nested in other mechanisms. A side effect of more control is that we can do other tricks too and we're playing with it (kind of fun).
>
> Hi Hans,
>
> Thanks for your explanations.
>
> Regarding footnotes, would it be possible to have a built-in support for writing the footnotes in the margin? (For instance, assuming that the layout is such that for instance the right margin takes 1/3 of the page width, then the footnotes would occupy the right margin, beginning at the top).
It depends on what you want. This works ok:
\setuplayout
[cutspace=5cm,
width=middle,
margin=4cm]
\setuptexttexts
[margin]
[] [{\directsetup{notabene}}]
\startsetups notabene
\vbox to \textheight \bgroup
\setupalign[tolerant]
\topskipcorrection
\placenotes[endnote][before=,after=]
\vfilll
\egroup
\stopsetups
\starttext
test \endnote{\input ward }\par
test \endnote{x}\par
test \endnote{x}\par
\setups{notaflush}
\stoptext
This one handles overflow (suboptimal, nicer is stepwise flushing) but
this one also flushes notes that have refs on the next page. It just
indicates the usual: most can be done in tex without too much hassle but
one always needs to think about the edge cases as users can drop
anything in there and all can interfere.
\newbox\MyNoteOverflow
\startsetups notabene
\setbox\scratchbox\vbox\bgroup
\setupalign[tolerant]
\ifvoid\MyNoteOverflow \else
\unvbox\MyNoteOverflow
\fi
\placenotes[endnote][before=,after=]
\egroup
\scratchdimen\dimexpr\textheight-.5\lineheight\relax
\ifdim\ht\scratchbox>\scratchdimen
\global\setbox\MyNoteOverflow\box\scratchbox
\setbox\scratchbox\vsplit \MyNoteOverflow to \scratchdimen
\fi
\vbox\bgroup
\topskipcorrection
\unvbox\scratchbox
\vfilll
\egroup
\stopsetups
\startsetups notaflush
\doloop {
\page
\ifvoid\MyNoteOverflow
\exitloop
\else
\null \page
\fi
}
\stopsetups
\starttext
test \endnote{\input ward }\par
test \endnote{x}\par
test \endnote{x}\par
\setups{notaflush}
\stoptext
Variants (i can make one but not with this warm weather) can use
selective flushing (all kinds of things are possible with notes) but
another challenge is to have an independent criterium hooked into the
page builder (when i'm done with playing with extensions regarding pars
i might give that a go ... as usual more a challenge than a need so i
need some motive).
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update
2020-07-31 8:32 Hans Hagen
2020-07-31 8:40 ` Taco Hoekwater
@ 2020-08-01 13:20 ` Otared Kavian
2020-08-01 14:17 ` Hans Hagen
2020-08-01 16:41 ` Henning Hraban Ramm
2020-08-02 3:30 ` Aditya Mahajan
2020-08-03 17:37 ` Pablo Rodriguez
3 siblings, 2 replies; 29+ messages in thread
From: Otared Kavian @ 2020-08-01 13:20 UTC (permalink / raw)
To: mailing list for ConTeXt users
> On 31 Jul 2020, at 10:32, Hans Hagen <j.hagen@xs4all.nl> wrote:
>
> […]
>
> Other work in progress is: better columns in itemize, esp proper footnote support (not that I ever need that but I know users do so ...), experiments work ok, but I need to check spacing. In general, footnotes (will) behave a bit better, especially those used nested in other mechanisms. A side effect of more control is that we can do other tricks too and we're playing with it (kind of fun).
Hi Hans,
Thanks for your explanations.
Regarding footnotes, would it be possible to have a built-in support for writing the footnotes in the margin? (For instance, assuming that the layout is such that for instance the right margin takes 1/3 of the page width, then the footnotes would occupy the right margin, beginning at the top).
Best regards: Otared
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update
2020-07-31 8:40 ` Taco Hoekwater
@ 2020-07-31 10:18 ` Hans Hagen
0 siblings, 0 replies; 29+ messages in thread
From: Hans Hagen @ 2020-07-31 10:18 UTC (permalink / raw)
To: mailing list for ConTeXt users, Taco Hoekwater
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: lmtx update
2020-07-31 8:32 Hans Hagen
@ 2020-07-31 8:40 ` Taco Hoekwater
2020-07-31 10:18 ` Hans Hagen
2020-08-01 13:20 ` Otared Kavian
` (2 subsequent siblings)
3 siblings, 1 reply; 29+ messages in thread
From: Taco Hoekwater @ 2020-07-31 8:40 UTC (permalink / raw)
To: mailing list for ConTeXt users
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> }
or would that still trigger the built-in freeze ?
>
> Of course it might have other side effects once in lmtx we everywhere expect freezing to be enabled. You can take a snapshot with:
>
> \freezeparagraphproperties : snapshot relevant parameters
> \defrostparagraphproperties : resets snapshot
>
> More efficient is snapshotting a subcategory:
>
> \updateparagraphproperties : all
> \updateparagraphpenalties : only penalties
> \updateparagraphdemerits : other than penalties
> \updateparagraphshapes : hangindent etc
>
> Don't use the low level commands that they use because we take plenty of time to experiment at that level and interfaces might evolve, for instance:
>
> \frozen\hangindent 30pt
> \frozen\hangafter 2
>
> is valid and will likely stay.
>
> We're talking of a conceptually rather different approach. Internally the engine is still doing the same things but we can control it a bit differently. Due to the way ConTeXt is set up, we can make such a paradigm shift without too much troubles. I'll wrap up more details in an article later.
>
> Other work in progress is: better columns in itemize, esp proper footnote support (not that I ever need that but I know users do so ...), experiments work ok, but I need to check spacing. In general, footnotes (will) behave a bit better, especially those used nested in other mechanisms. A side effect of more control is that we can do other tricks too and we're playing with it (kind of fun).
>
> More work in progress concerns paragraph wrappers and that will result in a rewrite of some existing mechanism (generic subsystems with instances), but that might as well go unnoticed.
>
> To give an idea of possibilities, here is an example:
>
> \definedescription[whatever][alternative=right:bottom]
>
> \startwhatever{just a small\\example}
> \input ward
> \stopwhatever
>
> No one ever requested it so see it an a quick and dirty example but don't hesitate to ask for more anyway (we like an occasional challenge).
>
> Anyway, it might take some weeks / iterations before all this settles down and now you can't say that we didn't warn you.
>
> So far,
>
> 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
> ___________________________________________________________________________________
Taco Hoekwater
Elvenkind BV
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
* lmtx update
@ 2020-07-31 8:32 Hans Hagen
2020-07-31 8:40 ` Taco Hoekwater
` (3 more replies)
0 siblings, 4 replies; 29+ messages in thread
From: Hans Hagen @ 2020-07-31 8:32 UTC (permalink / raw)
To: mailing list for ConTeXt users
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)
Of course it might have other side effects once in lmtx we everywhere
expect freezing to be enabled. You can take a snapshot with:
\freezeparagraphproperties : snapshot relevant parameters
\defrostparagraphproperties : resets snapshot
More efficient is snapshotting a subcategory:
\updateparagraphproperties : all
\updateparagraphpenalties : only penalties
\updateparagraphdemerits : other than penalties
\updateparagraphshapes : hangindent etc
Don't use the low level commands that they use because we take plenty of
time to experiment at that level and interfaces might evolve, for instance:
\frozen\hangindent 30pt
\frozen\hangafter 2
is valid and will likely stay.
We're talking of a conceptually rather different approach. Internally
the engine is still doing the same things but we can control it a bit
differently. Due to the way ConTeXt is set up, we can make such a
paradigm shift without too much troubles. I'll wrap up more details in
an article later.
Other work in progress is: better columns in itemize, esp proper
footnote support (not that I ever need that but I know users do so ...),
experiments work ok, but I need to check spacing. In general, footnotes
(will) behave a bit better, especially those used nested in other
mechanisms. A side effect of more control is that we can do other tricks
too and we're playing with it (kind of fun).
More work in progress concerns paragraph wrappers and that will result
in a rewrite of some existing mechanism (generic subsystems with
instances), but that might as well go unnoticed.
To give an idea of possibilities, here is an example:
\definedescription[whatever][alternative=right:bottom]
\startwhatever{just a small\\example}
\input ward
\stopwhatever
No one ever requested it so see it an a quick and dirty example but
don't hesitate to ask for more anyway (we like an occasional challenge).
Anyway, it might take some weeks / iterations before all this settles
down and now you can't say that we didn't warn you.
So far,
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 29+ messages in thread
end of thread, other threads:[~2023-02-06 17:21 UTC | newest]
Thread overview: 29+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <mailman.0.1629453601.23792.ntg-context@ntg.nl>
2021-08-22 22:10 ` lmtx update/t-vim (again) Benjamin Buchmuller via ntg-context
2021-08-22 22:21 ` Wolfgang Schuster via ntg-context
2021-08-23 6:19 ` Hans Hagen via ntg-context
2021-08-23 10:32 ` Benjamin Buchmuller via ntg-context
2021-08-23 17:42 ` Aditya Mahajan via ntg-context
2021-08-23 17:45 ` Hans Hagen via ntg-context
2021-08-25 2:45 ` Aditya Mahajan via ntg-context
2021-08-22 22:55 ` lmtx update 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
-- strict thread matches above, loose matches on Subject: below --
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
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
2020-07-31 8:32 Hans Hagen
2020-07-31 8:40 ` Taco Hoekwater
2020-07-31 10:18 ` Hans Hagen
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-02 3:30 ` Aditya Mahajan
2020-08-03 17:37 ` Pablo Rodriguez
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).