[NTG-context] Super slow installation

2023-05-29 Thread Thangalin via ntg-context
Hi,

Installation of a fresh copy of LMTX has gone from a few minutes to
about 30 minutes. Here's what I ran:

1. Open terminal
2. Change to root
3. cd /opt
4. mkdir context-2023-05-29
5. cd context-2023-05-29
6. wget "http://lmtx.pragma-ade.com/install-lmtx//texmf.zip;
7. unzip texmf.zip
8. chmod +x install.sh
9. ./install.sh

mtx-install | unzipping 'texmf-context.zip'
 518 files of 5180 done,   81058499 bytes, 0.403 seconds
 ... snip ...
5180 files of 5180 done,  171691491 bytes, 1.035 seconds
mtx-install | installing tex/texmf-context, 4924 files
mtx-install | new  :   0 % : 2447 :
tex/texmf-context/context-readme.txt
... snip ...
mtx-install | new  :  48 % :21898 :
tex/texmf-context/doc/context/sources/general/manuals/about/still-expanding-10.png

Getting to this point has taken shy of 15 minutes.

Any ideas what's going on or how to fix it?

Note that upgrading against the version prior to 2023.05.29 (i.e.,
without re-installing from scratch), the process happens pretty
quickly.

Thank you!
___
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] hyperlinks not working with current latest

2023-05-29 Thread Pablo Rodriguez via ntg-context
On 5/29/23 09:43, Hans Hagen via ntg-context wrote:
> On 5/28/2023 8:57 PM, Pablo Rodriguez via ntg-context wrote:
>> Dear list,
>>
>> in the following sample, hyperlinks for footnotest don’t work with
>> current latest (2023.05.28 18:57) with current LMTX (20230528):
>> [...]
>> Could anyone confirm this issue?
>
> i'll upload a fix later today (some sensitivity to an extra return value
> of a helper)

Many thanks for your fast fix, Hans.

Pablo

___
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] Cron /var/www/aanhet.net/context/bin/cron/context-mirror

2023-05-29 Thread Taco Hoekwater via ntg-context
Hi all,

Sorry about all these. The server had a network failure earlier today (fixed 
now)

Best wishes,
Taco

> On 29 May 2023, at 15:14, Cron Daemon via ntg-context  
> wrote:
> 
> rsync: getaddrinfo: rsync.pragma-ade.nl 873: Temporary failure in name 
> resolution
> rsync error: error in socket IO (code 10) at clientserver.c(139) 
> [Receiver=3.2.7]
> ___
> 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] \doifelseoddpage not working as expected

2023-05-29 Thread Henning Hraban Ramm via ntg-context

Am 29.05.23 um 16:47 schrieb Hans Hagen via ntg-context:
Is this also the right approach to check for the current page within a 
float placement?

Like
\startplacefigure[]
 \dontleavehmode\signalrightpage % necessary?
 \doifelserightpage{RIGHT}{LEFT}
 \doifelseoddpage  {ODD  }{EVEN}
\stopplacefigure
?

In my macros from 2015 I’m still using manual right/left page 
versions, and I’d like to enhance them.
I need e.g. different \offset values for \externalfigure depending on 
right/left page.
normally you will use "inner*" and "outer*" placement there as in other 
cases (which uses the same tricks)


I have one macro to place an page-width image with bleed, it uses 
\placefigure[top] and then \offset to move the image, so that it starts 
with bleed on the top side and with/without on the left side depending 
on a parameter that I change manually if the page breaking changes. The 
caption must stay within the type area – that works so far.
But it shouldn’t be necessary to define left/right manually, and that’s 
my question: if these \doifs work correctly within a float placement.


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] \doifelseoddpage not working as expected

2023-05-29 Thread Hans Hagen via ntg-context

On 5/29/2023 4:10 PM, Henning Hraban Ramm via ntg-context wrote:

Am 27.05.23 um 23:54 schrieb Hans Hagen via ntg-context:
You never know when tex will break a page unless you are explicit so 
you typeset the status too soon.


\setuppagenumbering[alternative=doublesided]
% \setuppagenumbering[alternative={singlesided,doublesided}]

\starttext
 \dorecurse{200}{
 \dontleavehmode\signalrightpage
 \doifelserightpage{RIGHT}{LEFT}
 \doifelseoddpage  {ODD  }{EVEN}
 \par
 }
\stoptext

The rightpage check combined with putting a signal at the spot where 
you test will work ok.


The odd/even test works as expected when you're in the page builder 
(wrapping up the page).


Is this also the right approach to check for the current page within a 
float placement?

Like
\startplacefigure[]
 \dontleavehmode\signalrightpage % necessary?
 \doifelserightpage{RIGHT}{LEFT}
 \doifelseoddpage  {ODD  }{EVEN}
\stopplacefigure
?

In my macros from 2015 I’m still using manual right/left page versions, 
and I’d like to enhance them.
I need e.g. different \offset values for \externalfigure depending on 
right/left page.
normally you will use "inner*" and "outer*" placement there as in other 
cases (which uses the same tricks)


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] \getbuffer without extra whitespace?

2023-05-29 Thread Wolfgang Schuster via ntg-context

Gerben Wierda via ntg-context schrieb am 29.05.2023 um 16:19:

If I do something like:

\startbuffer[version]20230529a\stopbuffer
Version: \getbuffer[version]-en

I get whitespace between the content of the buffer and “-en”

What is the proper LMTX way to do this?


You need the \inlinebuffer command

\starttext

\startbuffer[version]
20230529a
\stopbuffer

Version: \inlinebuffer[version]-en

\stoptext

but buffers aren't the right tool to store strings like version information.

One alternative solution is to set the string with the \setupdocument 
command.


\setupdocument
  [version=20230529a]

\starttext

Version: \documentvariable{version}-en

\stoptext

Wolfgang

___
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] \getbuffer without extra whitespace?

2023-05-29 Thread Gerben Wierda via ntg-context
If I do something like:

\startbuffer[version]20230529a\stopbuffer
Version: \getbuffer[version]-en

I get whitespace between the content of the buffer and “-en”

What is the proper LMTX way to do this?

Gerben Wierda (LinkedIn )
R Enterprise Architecture  (main site)
Book: Chess and the Art of Enterprise Architecture 
Book: Mastering ArchiMate 
___
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] \doifelseoddpage not working as expected

2023-05-29 Thread Henning Hraban Ramm via ntg-context

Am 27.05.23 um 23:54 schrieb Hans Hagen via ntg-context:
You never know when tex will break a page unless you are explicit so you 
typeset the status too soon.


\setuppagenumbering[alternative=doublesided]
% \setuppagenumbering[alternative={singlesided,doublesided}]

\starttext
     \dorecurse{200}{
     \dontleavehmode\signalrightpage
     \doifelserightpage{RIGHT}{LEFT}
     \doifelseoddpage  {ODD  }{EVEN}
     \par
     }
\stoptext

The rightpage check combined with putting a signal at the spot where you 
test will work ok.


The odd/even test works as expected when you're in the page builder 
(wrapping up the page).


Is this also the right approach to check for the current page within a 
float placement?

Like
\startplacefigure[]
\dontleavehmode\signalrightpage % necessary?
\doifelserightpage{RIGHT}{LEFT}
\doifelseoddpage  {ODD  }{EVEN}
\stopplacefigure
?

In my macros from 2015 I’m still using manual right/left page versions, 
and I’d like to enhance them.
I need e.g. different \offset values for \externalfigure depending on 
right/left page.


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
___


[NTG-context] Cron /var/www/aanhet.net/context/bin/cron/context-mirror

2023-05-29 Thread Cron Daemon via ntg-context
rsync: getaddrinfo: rsync.pragma-ade.nl 873: Temporary failure in name 
resolution
rsync error: error in socket IO (code 10) at clientserver.c(139) 
[Receiver=3.2.7]
___
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] Cron /var/www/aanhet.net/context/bin/cron/context-mirror

2023-05-29 Thread Cron Daemon via ntg-context
rsync: getaddrinfo: rsync.pragma-ade.nl 873: Temporary failure in name 
resolution
rsync error: error in socket IO (code 10) at clientserver.c(139) 
[Receiver=3.2.7]
___
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] Cron /var/www/aanhet.net/context/bin/cron/context-mirror

2023-05-29 Thread Cron Daemon via ntg-context
rsync: getaddrinfo: rsync.pragma-ade.nl 873: Temporary failure in name 
resolution
rsync error: error in socket IO (code 10) at clientserver.c(139) 
[Receiver=3.2.7]
___
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] Cron /var/www/aanhet.net/context/bin/cron/context-mirror

2023-05-29 Thread Cron Daemon via ntg-context
rsync: getaddrinfo: rsync.pragma-ade.nl 873: Temporary failure in name 
resolution
rsync error: error in socket IO (code 10) at clientserver.c(139) 
[Receiver=3.2.7]
___
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] Cron /var/www/aanhet.net/context/bin/cron/context-mirror

2023-05-29 Thread Cron Daemon via ntg-context
receiving incremental file list
 ./
 ctan.lsr
 document-2.htm
 download-1.htm
 download-2.htm
 logo-ade.png
 logo-cts.png
 logo-pod.png
 rss.xml
 show-fil.pdf
 context/latest/
 context/latest/cont-mpd.zip
 context/latest/cont-ppc.zip
 context/latest/cont-sci.zip
 context/latest/cont-tmf.zip
 context/latest/cont-tst.7z
 context/latest/cont-tst.tar.xz
 context/latest/cont-tst.zip
 
 sent 101,273 bytes  received 21,781,411 bytes  3,978,669.82 bytes/sec
 total size is 449,984,752  speedup is 20.56


Running archiver:

New dir: /var/www/aanhet.net/context//htdocs/archives/context-2023-05-29.16
121785175   
/var/www/aanhet.net/context//htdocs/archives/context-2023-05-29.16/latest
126745317   
/var/www/aanhet.net/context//htdocs/archives/context-2023-05-29.16/current
248534588   
/var/www/aanhet.net/context//htdocs/archives/context-2023-05-29.16
248534588   total
___
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] Cron /var/www/aanhet.net/context/bin/cron/context-mirror

2023-05-29 Thread Cron Daemon via ntg-context
rsync: getaddrinfo: rsync.pragma-ade.nl 873: Temporary failure in name 
resolution
rsync error: error in socket IO (code 10) at clientserver.c(139) 
[Receiver=3.2.7]
___
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] Cron /var/www/aanhet.net/context/bin/cron/context-mirror

2023-05-29 Thread Cron Daemon via ntg-context
rsync: getaddrinfo: rsync.pragma-ade.nl 873: Temporary failure in name 
resolution
rsync error: error in socket IO (code 10) at clientserver.c(139) 
[Receiver=3.2.7]
___
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] Cron /var/www/aanhet.net/context/bin/cron/context-mirror

2023-05-29 Thread Cron Daemon via ntg-context
rsync: getaddrinfo: rsync.pragma-ade.nl 873: Temporary failure in name 
resolution
rsync error: error in socket IO (code 10) at clientserver.c(139) 
[Receiver=3.2.7]
___
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] Cron /var/www/aanhet.net/context/bin/cron/context-mirror

2023-05-29 Thread Cron Daemon via ntg-context
rsync: getaddrinfo: rsync.pragma-ade.nl 873: Temporary failure in name 
resolution
rsync error: error in socket IO (code 10) at clientserver.c(139) 
[Receiver=3.2.7]
___
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] Cron /var/www/aanhet.net/context/bin/cron/context-mirror

2023-05-29 Thread Cron Daemon via ntg-context
rsync: getaddrinfo: rsync.pragma-ade.nl 873: Temporary failure in name 
resolution
rsync error: error in socket IO (code 10) at clientserver.c(139) 
[Receiver=3.2.7]
___
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] hyperlinks not working with current latest

2023-05-29 Thread Hans Hagen via ntg-context

On 5/28/2023 8:57 PM, Pablo Rodriguez via ntg-context wrote:

Dear list,

in the following sample, hyperlinks for footnotest don’t work with
current latest (2023.05.28 18:57) with current LMTX (20230528):

   \setupinteraction
 [state=start,
  focus=standard]
   \starttext
   \completecontent
   \dorecurse{5}
 {a\footnote{}}
   \stoptext

LuaTeX generates fine hyperlinks for footnotes.

My guess is that the issue is in the LuaMetaTeX binary.

Could anyone confirm this issue?
i'll upload a fix later today (some sensitivity to an extra return value 
of a helper)


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
___


[NTG-context] [ error installing fresh lmtx]

2023-05-29 Thread vm via ntg-context

using linux pop!os 22.04

https://www.pragma-ade.nl/install.htm

download
http://lmtx.pragma-ade.nl/install-lmtx/context-linux-64.zip

mkdir context
cd context
unzip context-linux-64.zip
sh install.sh


...
<+ 
/home/vm/context/tex/texmf-context/tex/context/base/mkiv/luat-sto.lua><+ 
/home/vm/context/tex/texmf-context/tex/context/base/mkiv/luat-ini.lua><+ 
/home/vm/context/tex/texmf-context/tex/context/base/mkiv/util-env.lua><+ 
/home/vm/context/tex/texmf-context/tex/context/base/mkiv/luat-env.lua>
resolvers   > lua > loading file 
'/home/vm/context/tex/texmf-context/tex/context/base/mkiv/luat-exe.lua' 
succeeded
resolvers   > lua > loading file 
'/home/vm/context/tex/texmf-context/tex/context/base/mkiv/luat-iop.lua' 
succeeded
resolvers   > lua > loading file 
'/home/vm/context/tex/texmf-context/tex/context/base/mkiv/trac-lmx.lua' 
succeeded
resolvers   > lua > loading file 
'/home/vm/context/tex/texmf-context/tex/context/base/mkiv/luat-mac.lua' 
succeeded
resolvers   > lua > loading file 
'/home/vm/context/tex/texmf-context/tex/context/base/mkiv/util-lib.lua' 
succeeded
resolvers   > lua > loading file 
'/home/vm/context/tex/texmf-context/tex/context/base/mkiv/lxml-tab.lua' 
succeeded
...ext/tex/texmf-context/tex/context/base/mkiv/lxml-lpt.lua:64: attempt 
to index a nil value (local 'xml')

stack traceback:
	...ext/tex/texmf-context/tex/context/base/mkiv/lxml-lpt.lua:64: in 
local 'code'
	...ext/tex/texmf-context/tex/context/base/mkiv/util-lua.lua:96: in 
field 'loadedluacode'
	...ext/tex/texmf-context/tex/context/base/mkiv/luat-env.lua:108: in 
field 'luafilechunk'
	...ext/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua:73: in 
function 'lua.registercode'

[\directlua]:1: in main chunk.
\registerctxluafile #1#2->\ctxlua {lua.registercode("#1","#2")}

l.94 \registerctxluafile{lxml-lpt}{}

?




(any hints?)
Thanks
.Floris
___
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] Cron /var/www/aanhet.net/context/bin/cron/context-mirror

2023-05-29 Thread Cron Daemon via ntg-context
rsync: getaddrinfo: rsync.pragma-ade.nl 873: Temporary failure in name 
resolution
rsync error: error in socket IO (code 10) at clientserver.c(139) 
[Receiver=3.2.7]
___
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] Cron /var/www/aanhet.net/context/bin/cron/context-mirror

2023-05-29 Thread Cron Daemon via ntg-context
rsync: getaddrinfo: rsync.pragma-ade.nl 873: Temporary failure in name 
resolution
rsync error: error in socket IO (code 10) at clientserver.c(139) 
[Receiver=3.2.7]
___
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] Cron /var/www/aanhet.net/context/bin/cron/context-mirror

2023-05-29 Thread Cron Daemon via ntg-context
rsync: getaddrinfo: rsync.pragma-ade.nl 873: Temporary failure in name 
resolution
rsync error: error in socket IO (code 10) at clientserver.c(139) 
[Receiver=3.2.7]
___
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
___