Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux

[Carlos via ntg-context]

On Sun, Mar 26, 2023 at 01:04:30PM +0200, Henning Hraban Ramm via ntg-context 
wrote:
> Am 25.03.23 um 23:42 schrieb Carlos via ntg-context:
> 
> > > > fonts   | names | 3092 afm files checked,   okay
> > > > fonts   | names | identifying tree font files with suffix 'AFM'
> > > > fonts   | names | scanning path 
> > > > '/home/ce/.texlive2023/texmf-config' for AFM files
> 
> > > > fonts   | names | variable 'OSFONTDIR' specifies path '/home/ce'
> > > > fonts   | names | variable 'OSFONTDIR' specifies path 
> > > > '/usr/share/fonts'
> > > > fonts   | names | globbing path '/home/ce/**.otf'
> 
> There is something strange here.
> Is maybe TEXMFHOME set?
> 
> Since you use a TeX live installation, some other texmfcnf.lua or texmf.cnf
> might interfere.
> Look into /usr/local/texlive/2023/
> 
> Since it scans everything in your home directory, maybe TEXMFHOME or
> OSFONTDIR is set to ~ (instead ~/texmf) there?
> 
> Hraban

I created an entirely different folder and placed the otf files right in it 
following Hans' advice on using directly otf rather than ttf 

The latter was used successfully under Void TeXLive prepackaged 2021 using a 
loadmapfile[texnansi-bandh-lucida.map] 

There was a texmfcnf.lua under the TEXMFLOCAL variable, and another one under 
TEXMFDIST. Got rid of the former but haven't tested it enough.

Thanks for bringing it up! 

It compiled fine, saved some rendering presumably from missing a  few otf files 
that I didn't have under Alpine. 
> ___
> 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
> ___

-- 
!07/11 PDP a ni deppart m'I  !pleH

___
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
___

Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux

[Carlos via ntg-context]

On Sat, Mar 25, 2023 at 09:26:36PM +0100, Hans Hagen via ntg-context wrote:
> On 3/25/2023 8:55 PM, Carlos via ntg-context wrote:
> > Hello list:
> > 
> > This is under a fresh TeXLive installation. Sort as to put aside any 
> > texlive prepackaged issues.
> > 
> > And the followign lines is the output of the error I've been having with 
> > the call of context on a recent texlive installation by both mtxrun 
> > --generate and luatools --generate right after.
> 
> there i no need to use luatools (it's something old from the early days)
> 
> what does
> 
>   mtxrun --generate --verbose
> 
> report (whre does it fail)
> 
> > 57 \starttext
> > 58
> > 59 \usetypescriptfile[type-lucida]
> > 60 \usetypescript[Lucida][texnansi]
> > 61 >>  \setupbodyfont[MyLucida, 10pt]
> > 62
> > 63 \input zapf
> > 64
> > 65 \input tufte
> 
> fwiw, lucida type one makes no sense any more because the opentype version
> is way better (and in the updated math setup in lmtx we didn't even look at
> it)
> 

Hans, your advice for using otf fonts worked. Thanks. 

system  > lua > compiling 
'/home/ce/.texlive2023/texmf-var/luametatex-cache/context/1b4da46d1f340757f9984eae810b1464/fonts/streams/lucidabrightregularotf-1.tma'
 into 
'/home/ce/.texlive2023/texmf-var/luametatex-cache/context/1b4da46d1f340757f9984eae810b1464/fonts/streams/lucidabrightregularotf-1.tmd'
system  > lua > dumping 
'/home/ce/.texlive2023/texmf-var/luametatex-cache/context/1b4da46d1f340757f9984eae810b1464/fonts/streams/lucidabrightregularotf-1.tma'
 into 
'/home/ce/.texlive2023/texmf-var/luametatex-cache/context/1b4da46d1f340757f9984eae810b1464/fonts/streams/lucidabrightregularotf-1.tmd'
 stripped

Not how I wanted it originally as in Void Linux with texnansi encoding and a 
TeXLive2021 prepackaged

mkiv lua stats  > loaded fonts: 4 files: lucidabrightregular.otf, 
lucidasansregular.otf, latinmodern-math.otf, lmroman12-regular.otf
mkiv lua stats  > font engine: otf 3.113, afm 1.513, tfm 1.000, 12 instances, 6 
shared in backend, 4 common vectors, 2 common hashes, load time 0.413 seconds 
mkiv lua stats  > used platform: linux-64, type: unix, binary subtree: usr
mkiv lua stats  > used engine: luatex version: 1.13, functionality level: 7418, 
banner: this is luatex, version 1.13.0 (tex live 2021/voidlinux)
mkiv lua stats  > used hash slots: 48145 of 65536 + 20
mkiv lua stats  > lua properties: engine: lua 5.3, used memory: 158 MB, ctx: 
158 MB, max: unknown MB, hash chars: min(64,40), symbol mask: utf (τεχ)


Or with otf under Alpine. but yes. otf rather than ttf  

backend > fonts > width units in 'SGVYNL+LucidaBright-Italic' are 2048, 
forcing 1000 instead
backend > fonts > width units in 'QRVECH+LucidaBright' are 2048, 
forcing 1000 instead
system  > start used files
system  > text: atestinlucida-OTF
system  > stop used files
system  > start used files
 


> > Is LuaLaTeX behaving the same way?
> > 
> > Answer: no.
> 
> no surprise because it doesn't use the same setup
> 
> what cache path does
> 
>   mtxrun --variables
> 
> report
> 
> 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 / 
> 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
> ___

-- 
The New Testament offers the basis for modern computer coding theory,
in the form of an affirmation of the binary number system.

But let your communication be Yea, yea; nay, nay:
for whatsoever is more than these cometh of evil.
-- Matthew 5:37

___
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
___

Re: [NTG-context] Spacing problem around decimal point

[Bruce Horrocks via ntg-context]

I also get the incorrect spacing on a Mac.

system  > ConTeXt  ver: 2023.03.20 17:07 LMTX  fmt: 2023.3.22  int: 
english/english


> On 26 Mar 2023, at 22:16, Jim via ntg-context  wrote:
> 
> Hi all,
> 
> Regrettably, I see the same problem and Gavin.
> 
> I am using TeXlive 2023 on Slackware64 15.0, for what that is worth.
> 
> 
>Jim
> 
> On Sun, Mar 26, 2023 at 17:36 (+0200), Günter Kolousek via ntg-context wrote:
> 
> 
>> Hi,
> 
>> I can confirm that the x64_64-linux from
> 
>> https://dl.contextgarden.net/build/luametatex/work/
> 
>> version works correctly. So, no excess spaces around the
>> decimal points at all.
> 
>> HTH
>> Günter
> 
>> Hans Hagen via ntg-context @ 2023-03-26 13:22 +02:
> 
>>> On 3/26/2023 4:20 AM, Gavin via ntg-context wrote:
 Hi List,
 I’m getting strange spaces around some decimal points after a clean
 LMTX
 install. MWE:
 \starttext
 \startformula
 v = \frac{1.32}{1.41} = 0.935
 \stopformula
 \stoptext
 This produces the result attached below. The 1.32 looks fine, but
 the next two
 numbers have excess space around the decimal point. Adding the line
   \showmakeup[mathglue] %\mathspacingmode=1
 to the preamble reveals that the second and third decimal points are
 being
 treated as binary operators. It’s very strang. Are others getting
 this?
>>> can you pick up a binary from:
> 
>>> https://dl.contextgarden.net/build/luametatex/work/
> 
>>> and test it?
> 
>>> Hans
> ___
> 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
> ___

—
Bruce Horrocks
Hampshire, UK

___
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
___

Re: [NTG-context] Spacing problem around decimal point

[Jim via ntg-context]

Hi all,

Regrettably, I see the same problem and Gavin.

I am using TeXlive 2023 on Slackware64 15.0, for what that is worth.


Jim

On Sun, Mar 26, 2023 at 17:36 (+0200), Günter Kolousek via ntg-context wrote:


> Hi,

> I can confirm that the x64_64-linux from

> https://dl.contextgarden.net/build/luametatex/work/

> version works correctly. So, no excess spaces around the
> decimal points at all.

> HTH
> Günter

> Hans Hagen via ntg-context @ 2023-03-26 13:22 +02:

>> On 3/26/2023 4:20 AM, Gavin via ntg-context wrote:
>>> Hi List,
>>> I’m getting strange spaces around some decimal points after a clean
>>> LMTX
>>> install. MWE:
>>> \starttext
>>> \startformula
>>> v = \frac{1.32}{1.41} = 0.935
>>> \stopformula
>>> \stoptext
>>> This produces the result attached below. The 1.32 looks fine, but
>>> the next two
>>> numbers have excess space around the decimal point. Adding the line
>>>\showmakeup[mathglue] %\mathspacingmode=1
>>> to the preamble reveals that the second and third decimal points are
>>> being
>>> treated as binary operators. It’s very strang. Are others getting
>>> this?
>> can you pick up a binary from:

>> https://dl.contextgarden.net/build/luametatex/work/

>> and test it?

>> Hans
___
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
___

Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux

[Carlos via ntg-context]

On Sun, Mar 26, 2023 at 03:21:35PM +0200, Hans Hagen via ntg-context wrote:
> On 3/26/2023 3:08 PM, Carlos via ntg-context wrote:
> > On Sun, Mar 26, 2023 at 01:04:30PM +0200, Henning Hraban Ramm via 
> > ntg-context wrote:
> > > Am 25.03.23 um 23:42 schrieb Carlos via ntg-context:
> > > 
> > > > > > fonts   | names | 3092 afm files checked,   okay
> > > > > > fonts   | names | identifying tree font files with suffix 
> > > > > > 'AFM'
> > > > > > fonts   | names | scanning path 
> > > > > > '/home/ce/.texlive2023/texmf-config' for AFM files
> > > 
> > > > > > fonts   | names | variable 'OSFONTDIR' specifies path 
> > > > > > '/home/ce'
> > > > > > fonts   | names | variable 'OSFONTDIR' specifies path 
> > > > > > '/usr/share/fonts'
> > > > > > fonts   | names | globbing path '/home/ce/**.otf'
> > > 
> > > There is something strange here.
> > > Is maybe TEXMFHOME set?
> > > 
> > > Since you use a TeX live installation, some other texmfcnf.lua or 
> > > texmf.cnf
> > > might interfere.
> > > Look into /usr/local/texlive/2023/
> > 
> > I'll check again to make sure. But keep in mind this issue predates the 
> > official TeX Live installation . I've been using the distro prepackaged for 
> > a while. And yes. It's always been there. Sort of like, it came with the 
> > system :)
> > > 
> > > Since it scans everything in your home directory, maybe TEXMFHOME or
> > > OSFONTDIR is set to ~ (instead ~/texmf) there?
> > 
> > But even if there was a conflict, it wouldn't justify to be scanninp up 
> > everything viciously.
> 
> Well, if fonts can be anywhere that means checking for them anywhere. TeX
> installations have some directory setup for a reason. Imagine that you set
> up the installation to include that wildcard path in TEXINPUITS then every
> run that whole tree would get scanned for a file you ask for and that is not
> in the current directory. The whole idea behind TDS and defining paths for
> specific kind of files it to limit lookups.

Hans, plesae… please, You know deep inside that the above paragraph does not 
make any sense even after writing it convincingly. The fact that fonts can be 
anywhere DOES NOT mean that a program whatever that program may be is following 
whatever TDS sets in place or is presumably setting in place.. or much less — 
regardless of fonts' location,  that a program out there needs to act 
erratically. Careless. To say the least. Bear with me in this one (I'm just a 
bit tired):

Look at the same issue from another system perspective. I said system 
perspective because simply put there is so much one can do whenever you're 
dealing with a multiuser program such as TeX Live. Bear wiht me here:

I have Void Linux on a spare system. Let's put aside for a second the 
inconsistencies surrounding texmfcnf.lua there. We can get back to it later And 
there's plenty of it taht can also be said.

Do you know what is the method used to handle this problem? By folder.

If I were to invoke mtxrun --script cache --erase it should behave accordingly. 
Or I'd expect it to act accordingly. The same with mtxrun --script font 
--reload Of course, it doesn't help if texmfcnf.lua sets anything else by doing 
otherwise.

Does it sound far-fetched? Maybe. But it certainly makes more sense than 
looking up everything under every imaginable worktree by which presumably there 
can be fonts. Which 100 percent of the time there's none.

But What fonts are to be found on cache and headers folders? tfm, afm, otf? 
come on!

But then again. Even in Void Linux (a system for which concurrent files lookups 
seem to be working now under the right expectations) threw errors back and 
forth with both context.lua mtx-context.lua and base.lua  unknown scripts,  
before eventually getting it right. (that may be a misnomer) I ought to say I 
got it right, I guess.

Were mtxrun --generate or mtxrun --script cache --erase called out? Of course.

Which led me to read about that pesky behavior here for example:

https://tug.org/pipermail/tex-live/2022-August/048375.html

and similarly

https://tex.stackexchange.com/questions/653913/context-from-texlive-2021-says-unknown-script-context-lua-or-mtx-context-lua

But the above was put aside. And there soon followed a matter-of-fact «it's not 
broken in TeX Live» statement.

Well. If looked at from that narow angle, yes, I guess. 

Recall this is with a prepackaged TeXLive or the one put out by the devs. And I 
was aware of that. Not the case here. I'm just mentioning it because that's the 
method used or what it's doing on that spare system as of now. Lookups for 
every folder.  

> 
> > So far I've had to move about 7-8 folders. About 6 of them are owned by 
> > root, the rest are owned by root but symlinked to user.
> 
> I would not do that, instead I'd fix ny OSFONTDIR path. Even with some
> directories moved you still end with plenty useless scanning.
>

I'm working on it.

> > And to top it off, after doing so, it didn't 

Re: [NTG-context] Spacing problem around decimal point

[Günter Kolousek via ntg-context]

Hi,

I can confirm that the x64_64-linux from

 https://dl.contextgarden.net/build/luametatex/work/

version works correctly. So, no excess spaces around the
decimal points at all.

HTH
Günter

Hans Hagen via ntg-context @ 2023-03-26 13:22 +02:


On 3/26/2023 4:20 AM, Gavin via ntg-context wrote:

Hi List,
I’m getting strange spaces around some decimal points after a 
clean LMTX

install. MWE:
\starttext
\startformula
v = \frac{1.32}{1.41} = 0.935
\stopformula
\stoptext
This produces the result attached below. The 1.32 looks fine, 
but the next two
numbers have excess space around the decimal point. Adding the 
line

   \showmakeup[mathglue] %\mathspacingmode=1
to the preamble reveals that the second and third decimal 
points are being
treated as binary operators. It’s very strang. Are others 
getting this?

can you pick up a binary from:

https://dl.contextgarden.net/build/luametatex/work/

and test it?

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 / 
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
___

___
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
___

Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux

[Hans Hagen via ntg-context]

On 3/26/2023 3:08 PM, Carlos via ntg-context wrote:

On Sun, Mar 26, 2023 at 01:04:30PM +0200, Henning Hraban Ramm via ntg-context 
wrote:

Am 25.03.23 um 23:42 schrieb Carlos via ntg-context:


fonts   | names | 3092 afm files checked,   okay
fonts   | names | identifying tree font files with suffix 'AFM'
fonts   | names | scanning path '/home/ce/.texlive2023/texmf-config' 
for AFM files



fonts   | names | variable 'OSFONTDIR' specifies path '/home/ce'
fonts   | names | variable 'OSFONTDIR' specifies path '/usr/share/fonts'
fonts   | names | globbing path '/home/ce/**.otf'


There is something strange here.
Is maybe TEXMFHOME set?

Since you use a TeX live installation, some other texmfcnf.lua or texmf.cnf
might interfere.
Look into /usr/local/texlive/2023/


I'll check again to make sure. But keep in mind this issue predates the 
official TeX Live installation . I've been using the distro prepackaged for a 
while. And yes. It's always been there. Sort of like, it came with the system :)


Since it scans everything in your home directory, maybe TEXMFHOME or
OSFONTDIR is set to ~ (instead ~/texmf) there?


But even if there was a conflict, it wouldn't justify to be scanninp up 
everything viciously.


Well, if fonts can be anywhere that means checking for them anywhere. 
TeX installations have some directory setup for a reason. Imagine that 
you set up the installation to include that wildcard path in TEXINPUITS 
then every run that whole tree would get scanned for a file you ask for 
and that is not in the current directory. The whole idea behind TDS and 
defining paths for specific kind of files it to limit lookups.



So far I've had to move about 7-8 folders. About 6 of them are owned by root, 
the rest are owned by root but symlinked to user.


I would not do that, instead I'd fix ny OSFONTDIR path. Even with some 
directories moved you still end with plenty useless scanning.



And to top it off, after doing so, it didn't stop there, heck no, it also 
wanted to snoop in a folder with cache and headers.

To be honest. I woudlnt' know what to make of it. If it's simply looking into 
the permissions of the directories first,  or the fact that it has a colon 
separated pattern. But. Then again. The other folders didn't have it.

I'll let you know.
What if you use the regular context installation (not texlive) and see 
what that does? Maybe that gives a clue.


(btw, the official texlive 2023 was tested on windows, linux and osx so 
there must be something special at your end.)


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 / 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
___

Re: [NTG-context] \writetolist not writing the number to the TOC

[Willi Egger via ntg-context]

Hello Hraban,

thank you. I missed this point. However, adding a dot behind the number does 
not appear to solve the problem. The title’s text still starts at the left 
margin which looks very odd.

Kind regards
Willi

> On 26 Mar 2023, at 12:51, Henning Hraban Ramm via ntg-context 
>  wrote:
> 
> Am 25.03.23 um 23:05 schrieb Willi Egger via ntg-context:
>> Good evening!
>> I have a setup in which I need to send info to the TOC:
>> Consider the following example:
>> \starttext
>> \starttitle[title=Contents]
>>   \placelist[chapter][criterium=all]
>> \stoptitle
>> \startchapter[title=Mychapter]
>>   \input knuth
>>   \startsubject[title=Subject will be in TOC]
>> \writetolist[chapter]{1}{I am in TOC!}
>> \input ward
>>   \stopsubject
>> \stopchapter
>> \stoptext
>> According to the Wiki I should get te number (1) in the TOC. Instead the 
>> text starts at the height of the chapter-numbering and is not carrying the 
>> given number.
>> Am I doing something wrong?
> 
> The wiki says:
> 
> “The default table of contents is combined list. To write to it one has to 
> choose the level to which it should be inserted: 
> \writetolist[chapter]{1.}{Chapter list entry A},
> \writetolist[section]{1.1}{Section list entry A}, etc.”
> 
> https://wiki.contextgarden.net/Command/writetolist
> 
> So maybe you need a dot?
> 
> Otherwise I don’t know.
> 
> Hraban
> ___
> 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
> ___

___
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
___

Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux

[Carlos via ntg-context]

On Sun, Mar 26, 2023 at 01:04:30PM +0200, Henning Hraban Ramm via ntg-context 
wrote:
> Am 25.03.23 um 23:42 schrieb Carlos via ntg-context:
> 
> > > > fonts   | names | 3092 afm files checked,   okay
> > > > fonts   | names | identifying tree font files with suffix 'AFM'
> > > > fonts   | names | scanning path 
> > > > '/home/ce/.texlive2023/texmf-config' for AFM files
> 
> > > > fonts   | names | variable 'OSFONTDIR' specifies path '/home/ce'
> > > > fonts   | names | variable 'OSFONTDIR' specifies path 
> > > > '/usr/share/fonts'
> > > > fonts   | names | globbing path '/home/ce/**.otf'
> 
> There is something strange here.
> Is maybe TEXMFHOME set?
> 
> Since you use a TeX live installation, some other texmfcnf.lua or texmf.cnf
> might interfere.
> Look into /usr/local/texlive/2023/

I'll check again to make sure. But keep in mind this issue predates the 
official TeX Live installation . I've been using the distro prepackaged for a 
while. And yes. It's always been there. Sort of like, it came with the system 
:) 
> 
> Since it scans everything in your home directory, maybe TEXMFHOME or
> OSFONTDIR is set to ~ (instead ~/texmf) there?

But even if there was a conflict, it wouldn't justify to be scanninp up 
everything viciously. 

So far I've had to move about 7-8 folders. About 6 of them are owned by root, 
the rest are owned by root but symlinked to user. 

And to top it off, after doing so, it didn't stop there, heck no, it also 
wanted to snoop in a folder with cache and headers. 

To be honest. I woudlnt' know what to make of it. If it's simply looking into 
the permissions of the directories first,  or the fact that it has a colon 
separated pattern. But. Then again. The other folders didn't have it. 

I'll let you know. 

Thank you Hraban 

Carlos
> Hraban
> ___
> 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
> ___

-- 
This file will self-destruct in five minutes.

___
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
___

Re: [NTG-context] Text editors

[Henning Hraban Ramm via ntg-context]

Am 26.03.23 um 10:22 schrieb Alexandre Christe via ntg-context:
I'm wondering what kind of typesetting system / syntax highlighting / 
completion you're using.


Active development happens for Visual Studio Code; I use VSCodium 
besides Atom.


Usable support for ConTeXt in Atom is available at 
https://codeberg.org/fiee/language-context
It’s a bit unkempt, since I stopped working on it when Atom was 
discontinued. I didn’t try the fork Pulsar yet (https://pulsar-edit.dev).

Atom’s git client is better than VSC’s, and I like its search bar better.

Also there’s COW: https://context-on-web.eu

Hraban
___
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
___

Re: [NTG-context] Spacing problem around decimal point

[Hans Hagen via ntg-context]

On 3/26/2023 4:20 AM, Gavin via ntg-context wrote:

Hi List,

I’m getting strange spaces around some decimal points after a clean LMTX 
install. MWE:

\starttext
\startformula
v = \frac{1.32}{1.41} = 0.935
\stopformula
\stoptext

This produces the result attached below. The 1.32 looks fine, but the next two 
numbers have excess space around the decimal point. Adding the line

   \showmakeup[mathglue] %\mathspacingmode=1

to the preamble reveals that the second and third decimal points are being 
treated as binary operators. It’s very strang. Are others getting this?

can you pick up a binary from:

https://dl.contextgarden.net/build/luametatex/work/

and test it?

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 / 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
___

Re: [NTG-context] registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux

[Henning Hraban Ramm via ntg-context]

Am 25.03.23 um 23:42 schrieb Carlos via ntg-context:


fonts   | names | 3092 afm files checked,   okay
fonts   | names | identifying tree font files with suffix 'AFM'
fonts   | names | scanning path '/home/ce/.texlive2023/texmf-config' 
for AFM files



fonts   | names | variable 'OSFONTDIR' specifies path '/home/ce'
fonts   | names | variable 'OSFONTDIR' specifies path '/usr/share/fonts'
fonts   | names | globbing path '/home/ce/**.otf'


There is something strange here.
Is maybe TEXMFHOME set?

Since you use a TeX live installation, some other texmfcnf.lua or 
texmf.cnf might interfere.

Look into /usr/local/texlive/2023/

Since it scans everything in your home directory, maybe TEXMFHOME or 
OSFONTDIR is set to ~ (instead ~/texmf) there?


Hraban
___
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
___

Re: [NTG-context] Text editors

[Nicola via ntg-context]

On 2023-03-26, Alexandre Christe via ntg-context  wrote:
> Dear ConTeXt users,
>
> I'm wondering what kind of typesetting system / syntax highlighting /
> completion you're using.
> [...]
> Open to anything from vim/neovim to emacs or more exotic. Maybe it would be
> nice to show the config. (And yes I've seen the Wiki page
> https://wiki.contextgarden.net/Text_Editors but I've the feeling some
> content is outdated.)

Vim offers good support for ConTeXt and MetaPost out of the box (I
maintain those filetypes). The Vim page in ConTeXt Garden is up
to date, afaict, but of course it is always better to check Vim's help
file for the most up-to-date information (`:help ft-context`).

Syntax highlighting is based on files generated by mtxrun: the help file
explains how to regenerating them if necessary, so you may stay in sync
with your ConTeXt installation.

Completion is kind of an orthogonal matter: there are quite a lot of
plugins for Vim if the built-in methods do not satisfy you. Again, the
wiki page has some suggestions (those may be a bit outdated, as new
completion plugins pop up all the time). Fwiw, I use MUcomplete.

Hope this helps!
Nicola

___
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
___

Re: [NTG-context] \writetolist not writing the number to the TOC

[Henning Hraban Ramm via ntg-context]

Am 25.03.23 um 23:05 schrieb Willi Egger via ntg-context:

Good evening!

I have a setup in which I need to send info to the TOC:

Consider the following example:

\starttext

\starttitle[title=Contents]
   \placelist[chapter][criterium=all]
\stoptitle

\startchapter[title=Mychapter]
   \input knuth
   \startsubject[title=Subject will be in TOC]
 \writetolist[chapter]{1}{I am in TOC!}
 \input ward
   \stopsubject
\stopchapter

\stoptext

According to the Wiki I should get te number (1) in the TOC. Instead the text 
starts at the height of the chapter-numbering and is not carrying the given 
number.

Am I doing something wrong?


The wiki says:

“The default table of contents is combined list. To write to it one has 
to choose the level to which it should be inserted: 
\writetolist[chapter]{1.}{Chapter list entry A},

\writetolist[section]{1.1}{Section list entry A}, etc.”

https://wiki.contextgarden.net/Command/writetolist

So maybe you need a dot?

Otherwise I don’t know.

Hraban
___
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
___

Re: [NTG-context] Spacing problem around decimal point

[Hans Hagen via ntg-context]

On 3/26/2023 4:20 AM, Gavin via ntg-context wrote:

Hi List,

I’m getting strange spaces around some decimal points after a clean LMTX 
install. MWE:

\starttext
\startformula
v = \frac{1.32}{1.41} = 0.935
\stopformula
\stoptext

This produces the result attached below. The 1.32 looks fine, but the next two 
numbers have excess space around the decimal point. Adding the line

   \showmakeup[mathglue] %\mathspacingmode=1

to the preamble reveals that the second and third decimal points are being 
treated as binary operators. It’s very strang. Are others getting this?

weird indeed

-
  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
___

Re: [NTG-context] \definemathfence broken in latest

[Hans Hagen via ntg-context]

On 3/26/2023 8:18 AM, Mikael Sundqvist via ntg-context wrote:


I think command=yes was changed into define=yes.

indeed. consistency across \definesomeghing

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 / 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
___

Re: [NTG-context] Text editors

[jbf via ntg-context]

Every user has his or her own preferred test editor. Over years I have 
used Emacs for just about everything except the kitchen sink, but not, 
as it happens, for ConTeXt.


For what it's worth here is what I use:

(1) TeXworks. All one has to do is indicate the correct path to ConText 
in the setup for this program, depending on your OS and where you have 
installed it, e.g. home/yourname/bin/context/tex/texmf-linux-64/bin if 
you are using Linux and have installed it in \bin. Then choose ConTeXt 
(LuaTeX) as the processing tool.


(2) But to make things a lot easier, I also use Federico's text expander 
Espanso 
https://espanso.org 
. This just saves so much time, especially for so 
many \start...\stop sequences.  For example, in espanso I might have:


# blockquote
  - trigger: ":bq"
    replace: |
  \startblockquote
  $|$
  \stopblockquote

And this means all I have to do is type :bq and as you can sense from 
the example above, I have the \start and \stop and intervening space all 
ready to work with.

Hope it helps!
Julian

On 26/3/23 19:22, Alexandre Christe via ntg-context wrote:

Dear ConTeXt users,

I'm wondering what kind of typesetting system / syntax highlighting / 
completion you're using.


I've been using myself the simple_Context package for SublimeText 
which I scavenged a while ago before it was made unavailable (I wanted 
to attach but it's too big for the list). But it's sort of a dead-end.


Open to anything from vim/neovim to emacs or more exotic. Maybe it 
would be nice to show the config. (And yes I've seen the Wiki page 
https://wiki.contextgarden.net/Text_Editorsbut I've the feeling some 
content is outdated.)


Thanks in advance,
Alex

___
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
__
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
___

[NTG-context] Text editors

[Alexandre Christe via ntg-context]

Dear ConTeXt users,

I'm wondering what kind of typesetting system / syntax highlighting /
completion you're using.

I've been using myself the simple_Context package for SublimeText which I
scavenged a while ago before it was made unavailable (I wanted to attach
but it's too big for the list). But it's sort of a dead-end.

Open to anything from vim/neovim to emacs or more exotic. Maybe it would be
nice to show the config. (And yes I've seen the Wiki page
https://wiki.contextgarden.net/Text_Editors but I've the feeling some
content is outdated.)

Thanks in advance,
Alex
___
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
___