[NTG-context] weekend update

[Hans Hagen via ntg-context]

Hi,

I uploaded a new version:

-- fix for hraban's svg image (one character patch)

-- more verbose link comments for pablo (for experimenting)

-- support for stacking at the tex end (maybe for presentations)

\starttext

\definestacking[one]
\definestacking[two]

\startbuffer
This is a test \stacking [one] {and a proof} of \stacking [two] 
{concept} indeed
\stacking [one] {\blackrule [width=4cm]} is it and the question is how 
\stacking

[two] {\scale [s=2] {fancy}} we can go

\startstacking[one]
\startformula
\sqrt{1+x}
\stopformula
\stopstacking

and how useful \stacking[two]{\inframed{it}} is.
\stopbuffer

\startstackingsteps[one,two,{one,two}]
\startTEXpage[offset=1ts]
\getbuffer
\stopTEXpage
\stopstackingsteps

\startTEXpage[offset=1ts] \setupstacking[criterium={one}] \getbuffer 
\stopTEXpage
\startTEXpage[offset=1ts] \setupstacking[criterium={two}] \getbuffer 
\stopTEXpage
\startTEXpage[offset=1ts] \setupstacking[criterium={one,two}] \getbuffer 
\stopTEXpage


\stoptext

-- support for more private pdf

\enabledirectives[backend.pdf.nounicode=noai]
\enabledirectives[backend.pdf.nounicode=nopilot]
\enabledirectives[backend.pdf.nounicode=justread]
\enabledirectives[backend.pdf.nounicode=✅]
\enabledirectives[backend.pdf.nounicode=✅❌]
\enabledirectives[backend.pdf.nounicode=❌]

\startTEXpage[offset=1ts]
\input tufte
\stopTEXpage

The last option can be handy when you don't want to make harvesting your 
documents too easy for these ai bots (as in cloud based pdf stuff). It's 
the first outcome of the multi-year, multi-stage, very scientific 
'inacessible pdf' project that Mikael S. and I recently started.


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://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] Re: update

[Emanuel Han via ntg-context]

Dear developers,
thanks for your hard work!

Thank you Wolfgang for the Japanese line break rule fix in line 831 of 
scrp-cjk.lua:
full_width_open = stretch_break, -- WS, was: nobreak_stretch_break_shrink,

Emanuel

On März 11 2024, at 7:23 pm, Pablo Rodriguez via ntg-context 
 wrote:
> On 3/11/24 18:48, Hans Hagen wrote:
> > Hi,
> >
> > Todays update has a fix for the compact mode slant interference (as
> > explained by Wolfgang a few days ago). Hopefully that works out well.
>
> Many thanks for that 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://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
> archive : https://github.com/contextgarden/context
> wiki : https://wiki.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://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] Re: update

[Pablo Rodriguez via ntg-context]

On 3/11/24 18:48, Hans Hagen wrote:
> Hi,
>
> Todays update has a fix for the compact mode slant interference (as
> explained by Wolfgang a few days ago). Hopefully that works out well.

Many thanks for that 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://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] Wiki update

[Taco Hoekwater]

Hi all,

I just updated the wiki ConTeXt to 20240108. 

The  tag on the wiki by default uses luametatex (LMTX), but if you 
want luatex instead (MKIV), you can still do that by using .

There have been some problems recently because Hans’ new binaries needed a 
newer version of various system libraries. 

I fixed that this morning after Hraban spotted the issue, but it means that 
there may be wiki pages with ConTeXt processing errors in them now. These can 
be recognised by either the colorised “error” output, or some cryptic “copy 
failed” message instead of the actual output.

If you see one of those pages, Edit it. For the  colorised “error” output you 
need to make a tiny change to the example itself (because that “error” output 
is correct as far as the wiki software can tell, so you have to force it to 
regenerate). For the “copy failed” case, you just have to start an edit and 
then immediately save again. The wiki will autogenerate any missing examples on 
save.

Best wishes,
Taco

— 
Taco Hoekwater  E: t...@bittext.nl
genderfluid (all pronouns)


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] wiki update: Modules

[Henning Hraban Ramm]

I updated the list of included modules in 
https://wiki.contextgarden.net/Modules and tried to understand what each 
does.


If you know matrices, could you perhaps update the page 
https://wiki.contextgarden.net/Matrix_in_maths to include the matrix 
module and the latest enhancements?


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] lmtx update

[Hans Hagen via ntg-context]

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
___

Re: [NTG-context] cannot update ConTeXt to 2022.09.16

[Pablo Rodriguez via ntg-context]

On 9/21/22 09:36, Hans Hagen via ntg-context wrote:
> On 9/21/2022 9:03 AM, Marco Patzer via ntg-context wrote:
>> Pablo Rodriguez via ntg-context  wrote:
>>
>>> Could anyone confirm the issue?
>>
>> I can confirm. On a fresh install I'm getting
>>
>>2022.09.11 20:44
> which is fine ... there is no later update ... Mojca and I are setting
> up repositories and that happens in parallel (including an alternative
> installer from git)

Hi Hans,

sorry, but I’m afraid I get from
https://github.com/contextgarden/context/blob/main/tex/context/base/mkxl/context.mkxl#L32
(supossedly comming from you):

  \immutable\edef\contextversion{2022.09.16 14:39}

BTW, it would be great if the installer could include all modules from
https://modules.contextgarden.net.

Many thanks for your help,

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] cannot update ConTeXt to 2022.09.16

[Hans Hagen via ntg-context]

On 9/21/2022 9:03 AM, Marco Patzer via ntg-context wrote:

On Mon, 19 Sep 2022 17:16:19 +0200
Pablo Rodriguez via ntg-context  wrote:


Could anyone confirm the issue?


I can confirm. On a fresh install I'm getting

   2022.09.11 20:44
which is fine ... there is no later update ... Mojca and I are setting 
up repositories and that happens in parallel (including an alternative 
installer from git)


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] cannot update ConTeXt to 2022.09.16

[Hans Hagen via ntg-context]

On 9/20/2022 5:21 PM, Pablo Rodriguez via ntg-context wrote:

On 9/19/22 18:23, Otared Kavian via ntg-context wrote:

Hi Pablo,

I had the same issue and, as this was discussed a few years or months
ago, after removing the three files with extension « .tma » the
update goes through normally.> On my machine, running MacOS X, I had to remove the 
following files:>

texmf.tma

texmf-osx-64.tma
texmf-context.tma


Hi Otared,

what is really weird, installing both brand-new versions for Win64 and
Linux64 is that I cannot get current latest from 2022.09.16 14:39 (but
only from 2022.09.11 20:44).

What am I doing wrong here?

Many thanks for your help,
only bins were updted (when we released), not the installer ... i need 
to do that when i'm at home and can access the dmz directly (and have 
bandwidth)


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] cannot update ConTeXt to 2022.09.16

[Marco Patzer via ntg-context]

On Mon, 19 Sep 2022 17:16:19 +0200
Pablo Rodriguez via ntg-context  wrote:

> Could anyone confirm the issue?

I can confirm. On a fresh install I'm getting

  2022.09.11 20:44

Marco
___
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] cannot update ConTeXt to 2022.09.16

[Max Chernoff via ntg-context]

Hi Pablo, Otared,

> On 9/19/22 18:23, Otared Kavian via ntg-context wrote:
> > Hi Pablo,
> >
> > I had the same issue and, as this was discussed a few years or months
> > ago, after removing the three files with extension « .tma » the
> > update goes through normally.> On my machine, running MacOS X, I had to 
> > remove the following files:>
> texmf.tma
> > texmf-osx-64.tma
> > texmf-context.tma
> 
> Hi Otared,
> 
> what is really weird, installing both brand-new versions for Win64 and
> Linux64 is that I cannot get current latest from 2022.09.16 14:39 (but
> only from 2022.09.11 20:44).

The exact same thing is happening on my end (Linux x86-64). I tried
upgrading using the regular method, then I tried deleting *.tma and
updating again. I still have version "2022.09.11 20:44". Not sure how to
fix it, but I guess at least you're not alone :)

-- Max
___
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] cannot update ConTeXt to 2022.09.16

[Pablo Rodriguez via ntg-context]

On 9/19/22 18:23, Otared Kavian via ntg-context wrote:
> Hi Pablo,
>
> I had the same issue and, as this was discussed a few years or months
> ago, after removing the three files with extension « .tma » the
> update goes through normally.> On my machine, running MacOS X, I had to 
> remove the following files:>
texmf.tma
> texmf-osx-64.tma
> texmf-context.tma

Hi Otared,

what is really weird, installing both brand-new versions for Win64 and
Linux64 is that I cannot get current latest from 2022.09.16 14:39 (but
only from 2022.09.11 20:44).

What am I doing wrong here?

Many thanks for your help,

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] cannot update ConTeXt to 2022.09.16

[Pablo Rodriguez via ntg-context]

On 9/19/22 18:23, Otared Kavian via ntg-context wrote:
> Hi Pablo,
>
> I had the same issue and, as this was discussed a few years or months
> ago, after removing the three files with extension « .tma » the
> update goes through normally. On my machine, running MacOS X, I had
> to remove the following files:
> texmf.tma
> texmf-osx-64.tma
> texmf-context.tma

Hi Otared,

that didn’t work for me.

No time to try a brand-new installation.

Many thanks for your help,

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] cannot update ConTeXt to 2022.09.16

[Otared Kavian via ntg-context]

Hi Pablo,

I had the same issue and, as this was discussed a few years or months ago, 
after removing the three files with extension « .tma » the update goes through 
normally.
On my machine, running MacOS X, I had to remove the following files:
texmf.tma
texmf-osx-64.tma
texmf-context.tma

Best regards: Otared

> On 19 Sep 2022, at 17:16, Pablo Rodriguez via ntg-context 
>  wrote:
> 
> Dear list,
> 
> after updating to latest from 2022.09.11 20:44 (altough LMTX was tagged
> as 20220918), I’m afraid I cannot update ConTeXt to 2022.09.16 (current
> latest according to https://www.pragma-ade.com/download-1.htm).
> 
> This happens to me with both Windows and Linux (both 64bit).
> 
> I guess this might be related to the issue with certificates and domains.
> 
> Could anyone confirm the issue?
> 
> Many thanks for your help,
> 
> 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
> ___

Otared Kavian
e-mail: ota...@gmail.com
Phone: +33 6 88 26 70 95



___
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] cannot update ConTeXt to 2022.09.16

[Pablo Rodriguez via ntg-context]

Dear list,

after updating to latest from 2022.09.11 20:44 (altough LMTX was tagged
as 20220918), I’m afraid I cannot update ConTeXt to 2022.09.16 (current
latest according to https://www.pragma-ade.com/download-1.htm).

This happens to me with both Windows and Linux (both 64bit).

I guess this might be related to the issue with certificates and domains.

Could anyone confirm the issue?

Many thanks for your help,

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
___

[NTG-context] no update

[Hans Hagen via ntg-context]

Hi,

no weekend update ... Mikael and I are working on / upgrading some math 
stuff (numbering) and don't want it to be too bad, as well as (new / 
improved) metapost stuff that we need to test first (and that also 
involves quite some experiments and documentation)


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
___

Re: [NTG-context] Wiki update: create a .vsix extension package for VisualStudio Code (or VSCodium)

[Hans Hagen via ntg-context]

On 5/5/2022 12:01 PM, mf via ntg-context wrote:


https://wiki.contextgarden.net/VSCode

Thanks!

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
___

[NTG-context] Wiki update: create a .vsix extension package for VisualStudio Code (or VSCodium)

[mf via ntg-context]

Hello list,

I just added some instructions to the WIKI to build an extension file 
for VSCode, starting from the code you find in the LMTX installation at


tex/texmf-context/context/data/vscode/extensions/context

You find them at

https://wiki.contextgarden.net/VSCode

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

Re: [NTG-context] lmtx update/t-vim (again)

[Aditya Mahajan via ntg-context]

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
___

Re: [NTG-context] lmtx update/t-vim (again)

[Hans Hagen via ntg-context]

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
___

Re: [NTG-context] lmtx update/t-vim (again)

[Aditya Mahajan via ntg-context]

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
___

Re: [NTG-context] lmtx update/t-vim (again)

[Benjamin Buchmuller via ntg-context]

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.




xxx-temp-vimR-0-error.log
Description: Binary data


xxx-temp-vimR-0.log
Description: Binary data


xxx-temp-vimR-1.log
Description: Binary data


> On Aug 23, 2021, at 08:19, Hans Hagen  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
> -

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

Re: [NTG-context] lmtx update

[Hans Hagen via ntg-context]

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
___

Re: [NTG-context] lmtx update/t-vim (again)

[Hans Hagen via ntg-context]

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
___

[NTG-context] lmtx update

[Benjamin Buchmuller via ntg-context]

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-requ...@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
___

Re: [NTG-context] lmtx update/t-vim (again)

[Wolfgang Schuster via ntg-context]

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
___

[NTG-context] lmtx update/t-vim (again)

[Benjamin Buchmuller via ntg-context]

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-requ...@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
___

Re: [NTG-context] lmtx update

[Hans Hagen via ntg-context]

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
___

Re: [NTG-context] lmtx update

[Aditya Mahajan via ntg-context]

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
___

[NTG-context] lmtx update

[Hans Hagen via ntg-context]

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
___

Re: [NTG-context] weekend update

[Richard Mahoney]

For a good number of years now I've been using P4D and 
P4V from Perforce for version control. As it happens it, one 
is able to control what ends up in the repository and what
is left out, thankfully. Regardless, this should be very helpful
Hans. It'll be great to be able to quickly scan the project files
that matter, knowing that all the clutter is safely kept somewhere
else. So thanks for this.

Perforce, by the way. (Freely available for smaller projects):

P4D

https://www.perforce.com/downloads/helix-core-p4d

P4V

https://www.perforce.com/downloads/helix-visual-client-p4v

And the diff tool is absolutely excellent (the reason I first
went with it):

https://www.perforce.com/downloads/visual-merge-tool


Best, Richard


--
*T* +6433121699  *M* +64210640216  *E* rmaho...@indica-et-buddhica.org
*IM* https://t.me/rmahoney  *W *https://indica-et-buddhica.org/**

*Indica et Buddhica  *Littledene  Bay Road  Oxford  NZ 
<https://indica-et-buddhica.org/>


- Original message -
From: Hans Hagen 
To: mailing list for ConTeXt users 
Subject: [NTG-context] weekend update
Date: Saturday, 24 July 2021 05:05

Hi,

This time the update has, appart from already mentioned mp fixes and 
additions, another new feature.

% runpath=texruns:whatever

% runpath=e:/temporary/texruns/runtest
% runpath=temp:texruns/runtest
% runpath=home:texruns/runtest

\starttext
 test
\stoptext

In context the first line can be used to control some aspects of the run 
and runpath (also as command line switch) will process the document 
elsewhere. The main reason for this feature is that when you have files 
in for instance a git repository (or export), you don't want the run 
path to be polluted by temporary files because everything can end up in 
the repository when it gets updates (after all these years I don't 
expect this pollution issue to be solved; svn is more explicit in what 
goes in).

So, for instance the manuals are on clean paths (on my machine i (am) 
put(ting) experiments, todo's etc under an ignored /private subpath 
which means that styles can still be found if needed).

The texruns: prefix resolves to an environment variable with the same 
name or when not set, to the temp directory. The temp: and home: 
prefixes resolve (as usual) to their counterparts (prefixes are a very 
old mkii mechanism but still useful).

When not present a path will be created, when no chdir is possible the 
run aborts.

There are probably some cases when resources are not found but that will 
be dealt with in due time. I might also update the underlying mechanisms 
at some point.

I already adapted some manuals so that means that when users process 
these themselves they will not see the runfiles fly to the temp path 
unless 'texruns' is configured. So be 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 / 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
___

[NTG-context] weekend update

[Hans Hagen]

Hi,

This time the update has, appart from already mentioned mp fixes and 
additions, another new feature.


% runpath=texruns:whatever

% runpath=e:/temporary/texruns/runtest
% runpath=temp:texruns/runtest
% runpath=home:texruns/runtest

\starttext
test
\stoptext

In context the first line can be used to control some aspects of the run 
and runpath (also as command line switch) will process the document 
elsewhere. The main reason for this feature is that when you have files 
in for instance a git repository (or export), you don't want the run 
path to be polluted by temporary files because everything can end up in 
the repository when it gets updates (after all these years I don't 
expect this pollution issue to be solved; svn is more explicit in what 
goes in).


So, for instance the manuals are on clean paths (on my machine i (am) 
put(ting) experiments, todo's etc under an ignored /private subpath 
which means that styles can still be found if needed).


The texruns: prefix resolves to an environment variable with the same 
name or when not set, to the temp directory. The temp: and home: 
prefixes resolve (as usual) to their counterparts (prefixes are a very 
old mkii mechanism but still useful).


When not present a path will be created, when no chdir is possible the 
run aborts.


There are probably some cases when resources are not found but that will 
be dealt with in due time. I might also update the underlying mechanisms 
at some point.


I already adapted some manuals so that means that when users process 
these themselves they will not see the runfiles fly to the temp path 
unless 'texruns' is configured. So be 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 / 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
___

[NTG-context] lmtx update: two experimental features

[Hans Hagen]

Hi,

I uploaded a new version. There are two new features that are 
experimental. This time we attempt to deal with the more tricky things 
and artifacts of the otherwise nice tex machinery we need to get rid of. 
One can rightfully argue that they are not really issues as one can work 
around them (and so they are never brought to attention) but why not 
make things better (cleaner) if we can.



(1) Languages: hyphenation normally uses a hyphen and the engine has 
some messy work-around-border-cases in the hyphenator. So, I wondered if 
we could improve that.


First of all, there can now be more than one hyphen character so here is 
the way to deal with it (the hyphenchar code is like the other 'codes'):


\hccode"002D = "002D
\hccode"2010 = "2010
\hccode"2013 = "2013
\hccode"2014 = "2014

This makes all these four into (kind of) compound word seperators:

\startTEXpage \hsize3mm
firstpart\char"002D secondpart\blank
firstpart\char"2010 secondpart\blank
firstpart\char"2013 secondpart\blank
firstpart\char"2014 secondpart
\stopTEXpage

will work ok. There are provisions for those characters being at the 
left and right edges. All is under low level (engine) option controls 
(compatibility and such) but currently I enable all. With a bit of 
definitions one can for the 002D and 2010 cases deal with pre/post 
variants .. the question is do we need that for more, if so, then I need 
to add some more code (doable).


This feature relates to Denis collection of German compound words and 
ligature prevention data. Dutch has the same issue. (Denis: we can ditch 
the compound word entries now, the ones with -.)


Also, this kind of automatism (keep in mind that normally tex won't 
hyphenate the first word in such a compound) is especially handy in 
cases where there is no control over the input as with xml (when we do 
have control you can use || as compound word marker).


(I'm wondering if we should deal with the typical somewhat archaic tex 
-- and --- in a different manner, but I'll come back to that.)



(2) Math: what is added is not so much an issue in traditional tex math 
usage which is for journals but as context is used for educational 
purposes and thereby has quite some tricks built in. Some of these jump 
through ugly hoops to get it done. Here I stick to color as example.


Just try this (notice the spacing):

\startTEXpage[offset=10pt]
\showmakeup[mathglue]%
\enableexperiments[simplegroups]%
$ a = b \color[red]{=} c \startcolor[blue]=\stopcolor d $\par
$ \sin \color[green]{(x)} = \sin {(x)} $\par
\disableexperiments[simplegroups]%
$ a = b \color[red]{=} c \startcolor[blue]=\stopcolor d $\par
$ \sin \color[green]{(x)} = \sin {(x)}$\par
\stopTEXpage

The 'simplegroups' experiment enables a more hybrid grouping model but 
we (read: Wolfgang, Aditya and I, but input is welcome) need to check 
for side effects carefully.


The 'mathglue' tracker is also new, and it exposes what actually goes 
on. It has to do with the fact that something grouped with { } creates a 
math list which enforces different spacing but in the case of color that 
is a side effect we don't want (of course it relates to how context 
implements the \color macro and one could work around it, but the 
problem is of a more general nature.



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
___

Re: [NTG-context] lmtx update / teaser

[Hans Hagen]

On 3/2/2021 11:15 AM, mf wrote:

Il 01/03/21 15:44, Hans Hagen ha scritto:


\starttext

\startuseMPgraphic{circle}
 lmt_parshape [
 path   = fullcircle scaled 136mm,
 offset = 2mm,
 bottomskip = - 1.5LineHeight,
 ] ;
\stopuseMPgraphic

\start
\startshapedparagraph[list=circle,mp=circle,repeat=yes,method=cycle]%


list=... refers to a previous \startparagraphshape definition, so mp=... 
tells ConTeXt that the definition is derived from MetaPost code instead.

You can go completely crazy with this:

\setupbodyfont[pagella,10pt]

\showframe

\setuplayout[width=middle,height=middle,footer=0pt]

\startuseMPgraphic{circle}
lmt_parshape [
 %  path   = fullcircle scaled 136mm,
path   = fullcircle scaled TextWidth randomized 2cm,
 %  offset = 2mm,
bottomskip = - 1.5LineHeight,
] ;
\stopuseMPgraphic

\starttext

\startshapedparagraph[mp=circle,repeat=yes,method=cycle]%
\setupalign[verytolerant,stretch,last]\dontcomplain
\dorecurse{100}{
{\darkred  \samplefile{tufte}}
{\darkgreen   \kerncharacters[.125]\samplefile{ward}}
{\darkblue\it  \samplefile{thuan}}
{\darkcyan\bf  \samplefile{zapf}}
{\darkmagenta \bi  \samplefile{sapolsky}}
{\darkyellow  \smallcaps   \samplefile{davis}}
\par % \blank
}
\stopshapedparagraph

\stoptext

It might work for a children book or so,

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
___

Re: [NTG-context] lmtx update / teaser

[Hans Hagen]

On 3/2/2021 11:15 AM, mf wrote:

Il 01/03/21 15:44, Hans Hagen ha scritto:


\starttext

\startuseMPgraphic{circle}
 lmt_parshape [
 path   = fullcircle scaled 136mm,
 offset = 2mm,
 bottomskip = - 1.5LineHeight,
 ] ;
\stopuseMPgraphic

\start
\startshapedparagraph[list=circle,mp=circle,repeat=yes,method=cycle]%


list=... refers to a previous \startparagraphshape definition, so mp=... 
tells ConTeXt that the definition is derived from MetaPost code instead.


you're right, the list= can be removed (you can do that and see that it 
still works)


Just mp=... could be enough, but maybe "list=xyz,mp=xyz" makes it clear 
that mp is used to get a parshape from MetaPost instead of a 
\startparagraphshape definition.



 \setupalign[verytolerant,stretch,last]\dontcomplain


What's the meaning of \dontcomplain? Why is it needed there?


I don't want to see messages about underful boxes cluttering my log (and 
such shapes tend to produce them).


BTW, \startparagraphshape, \stopparagraphshape, \startshapedparagraph, 
\stopshapedparagraph should be added to the .xml documentation files.


WOlfgang normally picks up these new thinsg and adds them but we update 
the xml files only periodically.


The "right", "left", "both", "copy", "repeat" syntax in 
\startparagraphshape is really handy.
I might actually add "metapost {name}" too and "delete n" to wipe out 
some previous ones. Rather trivial but we need to be able to say that we 
'added a new feature' occasionally. I couldn't yet think of more than 
'cycle' and 'repeat' but who knows what users want ... (like some 
autofit loop).


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
___

Re: [NTG-context] lmtx update / teaser

[mf]

Il 01/03/21 15:44, Hans Hagen ha scritto:


\starttext

\startuseMPgraphic{circle}
     lmt_parshape [
     path   = fullcircle scaled 136mm,
     offset = 2mm,
     bottomskip = - 1.5LineHeight,
     ] ;
\stopuseMPgraphic

\start
\startshapedparagraph[list=circle,mp=circle,repeat=yes,method=cycle]%


list=... refers to a previous \startparagraphshape definition, so mp=... 
tells ConTeXt that the definition is derived from MetaPost code instead.


Just mp=... could be enough, but maybe "list=xyz,mp=xyz" makes it clear 
that mp is used to get a parshape from MetaPost instead of a 
\startparagraphshape definition.



     \setupalign[verytolerant,stretch,last]\dontcomplain


What's the meaning of \dontcomplain? Why is it needed there?

BTW, \startparagraphshape, \stopparagraphshape, \startshapedparagraph, 
\stopshapedparagraph should be added to the .xml documentation files.


The "right", "left", "both", "copy", "repeat" syntax in 
\startparagraphshape is really handy.


Thanks,
Massi
___
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
___

Re: [NTG-context] lmtx update / teaser

[Hans Hagen]

On 3/1/2021 6:27 PM, Otared Kavian wrote:

Hi Hans,

Thank you for the new upload.

The teaser examples work fine, many thanks !
I have a question though: how can one center within a page a text, for example 
typeset in a circular shape? I tried with \startalignment, and also with 
\startplacefigure but none of these gives a centered circular shape.

Also I noticed that if one removes the comment at the end of 
\startshapedparagraph, or add a blank line after that, then the circular shape 
is destroyed: is this on purpose ?

\starttext

\startuseMPgraphic{circleBis}
lmt_parshape [
path   = fullcircle scaled 90mm,
offset = 2mm,
bottomskip = - 1.5LineHeight,
] ;
\stopuseMPgraphic

\startplacefigure[align=middle,number=no]
\framed[width=90mm,offset=2mm,align=normal]\bgroup
\startshapedparagraph
[list=circle,mp=circleBis,repeat=yes,method=repeat]%
\setupalign[verytolerant,stretch,last]\dontcomplain
{\darkred \samplefile{thuan}}
\stopshapedparagraph
\egroup
\stopplacefigure

\stoptext

We're talking parshapes here, think of

\parshape 2
  2mm 10cm
  4mm 12cm

or

\parshape 2
  options 1 % force a repeat
  2mm 10cm
  4mm 12cm

but then nicely wrapped in a macro. The circle is (cf metafun manual) 
converted into such a parshape. A parshape is forgotten when a new 
paragraph is started, but ... we have extra magic that revives them 
which is why the multi-page-par examples work too. The cycle and repeat 
methods do that (using abit diufferent tricks than the 20 year old one 
but not that different); these methods are independent of the parshape's 
repeat option itself, which is an engine feature.


Messing with left/right 'align' will also bring left/rightskip into the 
game so normally you will not do that. I admit it take a bit of 
imagination to get the picture. The 'last' keyword is some old context 
feature that centers the last line (which looks nicer in a circle) which

is using some parfillskip magic.

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
___

Re: [NTG-context] lmtx update / teaser

[Otared Kavian]

Hi Hans,

Thank you for the new upload.

The teaser examples work fine, many thanks !
I have a question though: how can one center within a page a text, for example 
typeset in a circular shape? I tried with \startalignment, and also with 
\startplacefigure but none of these gives a centered circular shape.

Also I noticed that if one removes the comment at the end of 
\startshapedparagraph, or add a blank line after that, then the circular shape 
is destroyed: is this on purpose ?

Best regards: Otared

% begin example-circular-shape.tex
\starttext

%\startuseMPgraphic{circle}
%   lmt_parshape [
%   path   = fullcircle scaled 136mm,
%   offset = 2mm,
%   bottomskip = - 1.5LineHeight,
%   ] ;
%\stopuseMPgraphic

\startuseMPgraphic{circleBis}
lmt_parshape [
path   = fullcircle scaled 90mm,
offset = 2mm,
bottomskip = - 1.5LineHeight,
] ;
\stopuseMPgraphic

\startalignment[middle]
%\startplacefigure[align=middle,number=no]
\start
\startshapedparagraph[list=circle,mp=circleBis,repeat=yes,method=repeat]%
\setupalign[verytolerant,stretch,last]
\dontcomplain
{\darkred \samplefile{thuan}}
\stopshapedparagraph
\stop
%\stopplacefigure
\stopalignment 

\stoptext
% end example-circular-shape.tex

> On 1 Mar 2021, at 15:44, Hans Hagen  wrote:
> 
> Hi,
> 
> I uploaded a new lmtx. As I'm currently going through the metafun todo files 
> I ended up at the fancy shape part (parshapes) running over multiple 
> paragraphs and decided to provide a (kind of low level) interface that 
> integrates that. The example code is a few decades old but still works ok (i 
> might try to improve them a bit some day). Anyway, here is a teaser:
> 
> \starttext
> 
> \startuseMPgraphic{circle}
>lmt_parshape [
>path   = fullcircle scaled 136mm,
>offset = 2mm,
>bottomskip = - 1.5LineHeight,
>] ;
> \stopuseMPgraphic
> 
> \start
> \startshapedparagraph[list=circle,mp=circle,repeat=yes,method=cycle]%
>\setupalign[verytolerant,stretch,last]\dontcomplain
>{\darkred \samplefile{tufte}}\par
>{\darkgreen   \samplefile{tufte}}\par
>{\darkblue\samplefile{tufte}}\par
>{\darkcyan\samplefile{tufte}}\par
>{\darkmagenta \samplefile{tufte}}\par
> \stopshapedparagraph
> \stop
> 
> \page
> 
> \start
> \startshapedparagraph[list=circle,mp=circle,repeat=yes,method=repeat]%
>\setupalign[verytolerant,stretch,last]\dontcomplain
>{\darkred \samplefile{tufte}}
>{\darkgreen   \samplefile{tufte}}
>{\darkblue\samplefile{tufte}}
>{\darkcyan\samplefile{tufte}}
>{\darkmagenta \samplefile{tufte}}
> \stopshapedparagraph
> \stop
> 
> \stoptext
> 
> The interface is still somewhat rough (no grouping for instance, not a real 
> envrionment so that might change) but seems to work ok. One can also go the 
> tex route and say:
> 
> \startparagraphshape[test]
>left 1mm right 1mm
>left 2mm right 2mm
>left 3mm right 3mm
>copy 8
>left 4mm right 4mm
>left 5mm right 5mm
>left 5mm hsize 10cm
> \stopparagraphshape
> 
> or
> 
> \startparagraphshape[test]
>left 1mm right 1mm
>right 3mm
>left 5mm right 5mm
>repeat
> \stopparagraphshape
> 
> or
> 
> \startparagraphshape[test]
>both 1mm both 2mm both 3mm both 4mm both 5mm both 6mm
>both 7mm both 6mm both 5mm both 4mm both 3mm both 2mm
> \stopparagraphshape
> 
> or
> 
> \startparagraphshape[test-repeat]
>both 1mm both 2mm both 3mm both 4mm both 5mm both 6mm
>both 7mm both 6mm both 5mm both 4mm both 3mm both 2mm
>repeat
> \stopparagraphshape
> 
> and use that with:
> 
> \startshapedparagraph[list=test]
>\dorecurse{8}{\showparagraphshape\samplefile{tufte} \par}
> \stopshapedparagraph
> 
> or
> 
> \startshapedparagraph[list=test-repeat]
>\dorecurse{8}{\showparagraphshape\samplefile{tufte} \par}
> \stopshapedparagraph
> 
> Some more info is in the lowlevel-paragrsph document (part of the low level 
> series).
> 
> This kind of features falls into the category 'fancy' (no one reqtested it), 
> nice for posters and covers. It might evolve depending on needs for fancy 
> features, but as said, it's currently a side track of metafun, so it's also 
> in the category 'fun'. It's code for 'controlled' usage.
> 
> 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  : 

[NTG-context] lmtx update / teaser

[Hans Hagen]

Hi,

I uploaded a new lmtx. As I'm currently going through the metafun todo 
files I ended up at the fancy shape part (parshapes) running over 
multiple paragraphs and decided to provide a (kind of low level) 
interface that integrates that. The example code is a few decades old 
but still works ok (i might try to improve them a bit some day). Anyway, 
here is a teaser:


\starttext

\startuseMPgraphic{circle}
lmt_parshape [
path   = fullcircle scaled 136mm,
offset = 2mm,
bottomskip = - 1.5LineHeight,
] ;
\stopuseMPgraphic

\start
\startshapedparagraph[list=circle,mp=circle,repeat=yes,method=cycle]%
\setupalign[verytolerant,stretch,last]\dontcomplain
{\darkred \samplefile{tufte}}\par
{\darkgreen   \samplefile{tufte}}\par
{\darkblue\samplefile{tufte}}\par
{\darkcyan\samplefile{tufte}}\par
{\darkmagenta \samplefile{tufte}}\par
\stopshapedparagraph
\stop

\page

\start
\startshapedparagraph[list=circle,mp=circle,repeat=yes,method=repeat]%
\setupalign[verytolerant,stretch,last]\dontcomplain
{\darkred \samplefile{tufte}}
{\darkgreen   \samplefile{tufte}}
{\darkblue\samplefile{tufte}}
{\darkcyan\samplefile{tufte}}
{\darkmagenta \samplefile{tufte}}
\stopshapedparagraph
\stop

\stoptext

The interface is still somewhat rough (no grouping for instance, not a 
real envrionment so that might change) but seems to work ok. One can 
also go the tex route and say:


\startparagraphshape[test]
left 1mm right 1mm
left 2mm right 2mm
left 3mm right 3mm
copy 8
left 4mm right 4mm
left 5mm right 5mm
left 5mm hsize 10cm
\stopparagraphshape

or

\startparagraphshape[test]
left 1mm right 1mm
right 3mm
left 5mm right 5mm
repeat
\stopparagraphshape

or

\startparagraphshape[test]
both 1mm both 2mm both 3mm both 4mm both 5mm both 6mm
both 7mm both 6mm both 5mm both 4mm both 3mm both 2mm
\stopparagraphshape

or

\startparagraphshape[test-repeat]
both 1mm both 2mm both 3mm both 4mm both 5mm both 6mm
both 7mm both 6mm both 5mm both 4mm both 3mm both 2mm
repeat
\stopparagraphshape

and use that with:

\startshapedparagraph[list=test]
\dorecurse{8}{\showparagraphshape\samplefile{tufte} \par}
\stopshapedparagraph

or

\startshapedparagraph[list=test-repeat]
\dorecurse{8}{\showparagraphshape\samplefile{tufte} \par}
\stopshapedparagraph

Some more info is in the lowlevel-paragrsph document (part of the low 
level series).


This kind of features falls into the category 'fancy' (no one reqtested 
it), nice for posters and covers. It might evolve depending on needs for 
fancy features, but as said, it's currently a side track of metafun, so 
it's also in the category 'fun'. It's code for 'controlled' usage.


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
___

[NTG-context] LMTX update 2020.11.17 ----> 11.19 | Paragraph indenting

[Richard Mahoney]

Hello,

I noticed yesterday that paragraph indenting appears to have changed
between
LMTX 2020.11.17 & 11.19. Usually the first paragraph after a section
heading
does not indent, as it does with all subsequent paragraphs. With 11.19
the first
paragraph does have an indent. I've had to revert to 11.17.


Best, Richard




-- 
T +6433121699  M +64210640216  E rmaho...@indica-et-buddhica.org
IM https://t.me/rmahoney  W https://indica-et-buddhica.org/


Indica et Buddhica  Littledene  Bay Road  Oxford  NZ
___
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
___

Re: [NTG-context] LMTX update 2020.11.17 ----> 11.19 | Paragraph indenting

[Pablo Rodriguez]

On 11/21/20 10:44 PM, Richard Mahoney wrote:
> Hello,
>
> I noticed yesterday that paragraph indenting appears to have changed between
> LMTX 2020.11.17 & 11.19. Usually the first paragraph after a section heading
> does not indent, as it does with all subsequent paragraphs. With 11.19
> the first  paragraph does have an indent. I've had to revert to 11.17.

Hi Richard,

Hans provided a patch at
https://mailman.ntg.nl/pipermail/ntg-context/2020/100284.html.

Choose the more correct one (as described by him, the second one) and
place in cont-new.mkiv, right before the final \protect.

Run "mtxrun --script cache --erase &&  mtxrun --generate" (so delete
cache and generate the basic files) and indenting will work again.

I hope it helps,

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
___

Re: [NTG-context] cannot update LMTX

[Pablo Rodriguez]

On 11/4/20 8:41 PM, Otared Kavian wrote:
> Hi Pablo,
>
> For some unknown reason despite having tried to update lmtx several
> times, I still have version 2020.09.20 23:02.
Hi Otared,

this is exactly the same version I have.

> Indeed I do a backup before any update in order to be able to go
> back to a working version…
It is a reasonable practice, as one never knows what could go wrong.

> What did you do in order to get version 2020.11.04 09:40 ?

I did a fresh install (as Sylvain suggested). Although I only wanted to
test that a fresh install was working.

I’m going to wait until I upgrade my local version. The backup is
already done.

Many thanks for your reply,

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
___

Re: [NTG-context] cannot update LMTX

[Otared Kavian]

Hi Pablo,

For some unknown reason despite having tried to update lmtx several times, I 
still have version 2020.09.20 23:02.
Indeed I do a backup before any update in order to be able to go back to a 
working version…

What did you do in order to get version 2020.11.04 09:40 ?

Best regards: Otared

> On 4 Nov 2020, at 16:38, Pablo Rodriguez  wrote:
> 
> On 11/4/20 4:18 PM, Otared Kavian wrote:
>> Hi Pablo,
>> 
>> I get the same result as you. I think the reason is that Hans has not
>> yet issued a newer version (he said in a message a few days ago that
>> by mistake he might have uploaded a new version, but that we should
>> be careful not to update yet…).
> 
> Hi Otared,
> 
> current latest is from today (2020.11.04 09:40).
> 
> I read the message and this is why I checked a version newer than
> 2020.10.30 (in both Linux and Windows) before asking about the issue.
> 
> I perform a backup before updating ConTeXt, so experimental versions
> should be no problem for me.
> 
> Many thanks for your help,
> 
> 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
> ___

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

Re: [NTG-context] cannot update LMTX

[Pablo Rodriguez]

On 11/4/20 4:18 PM, Otared Kavian wrote:
> Hi Pablo,
>
> I get the same result as you. I think the reason is that Hans has not
> yet issued a newer version (he said in a message a few days ago that
> by mistake he might have uploaded a new version, but that we should
> be careful not to update yet…).

Hi Otared,

current latest is from today (2020.11.04 09:40).

I read the message and this is why I checked a version newer than
2020.10.30 (in both Linux and Windows) before asking about the issue.

I perform a backup before updating ConTeXt, so experimental versions
should be no problem for me.

Many thanks for your help,

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
___

Re: [NTG-context] cannot update LMTX

[Otared Kavian]

Hi Pablo,

I get the same result as you. I think the reason is that Hans has not yet 
issued a newer version (he said in a message a few days ago that by mistake he 
might have uploaded a new version, but that we should be careful not to update 
yet…).

Best regards: Otared

> On 4 Nov 2020, at 16:10, Pablo Rodriguez  wrote:
> 
> Dear list,
> 
> after latest from 2020.09.20, I afraid I get this error when running
> install.sh on Linux or install.bat on Windows (both 64bit):
> 
> mtx-install | updating tex/texmf, 1541 files
> mtx-install | updating tex/texmf-context, 3757 files
> mtx-install | changed  :   0 % :24110 :
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua
> mtx-install |
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua,
> trying again:
> mtx-install | changed  :   0 % :24110 :
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua
> mtx-install |
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua,
> trying again:
> mtx-install | changed  :   0 % :24110 :
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua
> mtx-install |
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua,
> trying again:
> mtx-install | changed  :   0 % :24110 :
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua
> mtx-install |
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua,
> trying again:
> mtx-install | changed  :   0 % :24110 :
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua
> mtx-install |
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua,
> try again later:
> 
> If you want to run ConTeXt everywhere, you need to adapt the path, like:
> 
> I don’t know what has changed to prevent the update.
> 
> Could anyone confirm this issue with current LMTX?
> 
> Many thanks for your help,
> 
> 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
> ___

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

Re: [NTG-context] cannot update LMTX

[Sylvain Hubert]

Here a fresh standalone installed an hour ago doesn't seem to have the
problem.

On Wed, 4 Nov 2020 at 16:11, Pablo Rodriguez  wrote:

> Dear list,
>
> after latest from 2020.09.20, I afraid I get this error when running
> install.sh on Linux or install.bat on Windows (both 64bit):
>
> mtx-install | updating tex/texmf, 1541 files
> mtx-install | updating tex/texmf-context, 3757 files
> mtx-install | changed  :   0 % :24110 :
>
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua
> mtx-install |
>
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua,
> trying again:
> mtx-install | changed  :   0 % :24110 :
>
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua
> mtx-install |
>
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua,
> trying again:
> mtx-install | changed  :   0 % :24110 :
>
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua
> mtx-install |
>
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua,
> trying again:
> mtx-install | changed  :   0 % :24110 :
>
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua
> mtx-install |
>
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua,
> trying again:
> mtx-install | changed  :   0 % :24110 :
>
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua
> mtx-install |
>
> tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua,
> try again later:
>
> If you want to run ConTeXt everywhere, you need to adapt the path, like:
>
> I don’t know what has changed to prevent the update.
>
> Could anyone confirm this issue with current LMTX?
>
> Many thanks for your help,
>
> 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
>
> ___
>
___
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
___

[NTG-context] cannot update LMTX

[Pablo Rodriguez]

Dear list,

after latest from 2020.09.20, I afraid I get this error when running
install.sh on Linux or install.bat on Windows (both 64bit):

mtx-install | updating tex/texmf, 1541 files
mtx-install | updating tex/texmf-context, 3757 files
mtx-install | changed  :   0 % :24110 :
tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua
mtx-install |
tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua,
trying again:
mtx-install | changed  :   0 % :24110 :
tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua
mtx-install |
tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua,
trying again:
mtx-install | changed  :   0 % :24110 :
tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua
mtx-install |
tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua,
trying again:
mtx-install | changed  :   0 % :24110 :
tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua
mtx-install |
tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua,
trying again:
mtx-install | changed  :   0 % :24110 :
tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua
mtx-install |
tex/texmf-context/context/data/scite/context/lexers/data/scite-context-data-context.lua,
try again later:

If you want to run ConTeXt everywhere, you need to adapt the path, like:

I don’t know what has changed to prevent the update.

Could anyone confirm this issue with current LMTX?

Many thanks for your help,

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
___

Re: [NTG-context] lmtx update

[Eduardo Bohoyo]

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
___

Re: [NTG-context] lmtx update

[Eduardo Bohoyo]

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
___

Re: [NTG-context] lmtx update

[Wolfgang Schuster]

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
___

Re: [NTG-context] lmtx update

[Eduardo Bohoyo]

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
___

Re: [NTG-context] lmtx update

[Wolfgang Schuster]

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
___

[NTG-context] lmtx update

[ebohoyod]

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.


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

Re: [NTG-context] lmtx update

[Pablo Rodriguez]

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
___

Re: [NTG-context] lmtx update

[Aditya Mahajan]

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
___

Re: [NTG-context] lmtx update

[Otared Kavian]

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  wrote:
> 
> 
>> Am 01.08.2020 um 15:20 schrieb Otared Kavian :
>> 
>> 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
___

Re: [NTG-context] lmtx update

[Henning Hraban Ramm]

> Am 01.08.2020 um 15:20 schrieb Otared Kavian :
> 
> 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
___

Re: [NTG-context] lmtx update

[Otared Kavian]

> On 1 Aug 2020, at 16:17, Hans Hagen  wrote:
> 
> On 8/1/2020 3:20 PM, Otared Kavian wrote:
>>> On 31 Jul 2020, at 10:32, Hans Hagen  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
___

Re: [NTG-context] lmtx update

[Hans Hagen]

On 8/1/2020 3:20 PM, Otared Kavian wrote:

On 31 Jul 2020, at 10:32, Hans Hagen  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
___

Re: [NTG-context] lmtx update

[Otared Kavian]

> On 31 Jul 2020, at 10:32, Hans Hagen  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
___

Re: [NTG-context] lmtx update

[Hans Hagen]

On 7/31/2020 10:40 AM, Taco Hoekwater wrote:

Hi Hans,


On 31 Jul 2020, at 10:32, 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.

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 ..  }


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
___

Re: [NTG-context] lmtx update

[Taco Hoekwater]

Hi Hans,

> On 31 Jul 2020, at 10:32, 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.
> 
> 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 ..  }

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
___

[NTG-context] lmtx update

[Hans Hagen]

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
___

Re: [NTG-context] wiki update - status

[Aditya Mahajan]

On Mon, 8 Jun 2020, Garulfo wrote:


- Remove former "manually made links bar" at the top of the pages
  current structure should be enough now have an easier understanding of
  the wiki structure.


Along that line, we should also considering fixing the getting started navbox 
or removing it altogether. It used to have a nice visual layout, but that was 
lost when upgrading the wiki. In the current form, it uses too much vertical 
space and it might be redundant with the new wiki structure.

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
___

Re: [NTG-context] wiki update - status

[Marcus Vinicius Mesquita]

So much better! Thank you very much for the effort!

Greetings

Marcus Vinicius

On Sun, Jun 7, 2020, 19:05 Garulfo  wrote:

> Hi all,
>
> New source browser is nice ! Thanks a lot.
>
> After level 1 (Main Page / Download and Install / Documentation /
> Mailing lists), I mostly finished a review of level 2 (and some level 3)
> pages.
>
> Several tweaks all over the place like:
>
> - Fonts: full update for newcomers,
> - Try to be responsive "enough" for smartphone
> - More homogeneous style / theme
> - Old Content category and tag pages, update dead links
> - Layout:
>- do the todo, like merging content of paper setup + paper sizes pages
>- complete the flow with imposition
>- rework the "Further reading section", add PDF links and so on
> - Programming & DB:
>- Gather "Calling Lua from TeX" and "Calling TeX from Lua"
>  (section +links) in a same page
> - Tools:
>- segregate "core tools" and "additional tools"
>- highlight existence of mtxrun and context scripts pages
> - Remove former "manually made links bar" at the top of the pages
>current structure should be enough now have an easier understanding of
>the wiki structure.
>
> Thanks for your help Taco, Hans, Aditya, Hraban, Tomáš.
>
> I hope that this will help to improve the reception of users and their
> willingness to contribute.
>
> Bye.
>
> ___
> 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
___

Re: [NTG-context] wiki update - status

[Hans Hagen]

On 6/8/2020 12:05 AM, Garulfo wrote:

Hi all,

New source browser is nice ! Thanks a lot.

After level 1 (Main Page / Download and Install / Documentation / 
Mailing lists), I mostly finished a review of level 2 (and some level 3) 
pages.


Several tweaks all over the place like:

- Fonts: full update for newcomers,
- Try to be responsive "enough" for smartphone
- More homogeneous style / theme
- Old Content category and tag pages, update dead links
- Layout:
   - do the todo, like merging content of paper setup + paper sizes pages
   - complete the flow with imposition
   - rework the "Further reading section", add PDF links and so on
- Programming & DB:
   - Gather "Calling Lua from TeX" and "Calling TeX from Lua"
     (section +links) in a same page
- Tools:
   - segregate "core tools" and "additional tools"
   - highlight existence of mtxrun and context scripts pages
- Remove former "manually made links bar" at the top of the pages
   current structure should be enough now have an easier understanding of
   the wiki structure.

Thanks for your help Taco, Hans, Aditya, Hraban, Tomáš.

I hope that this will help to improve the reception of users and their 
willingness to contribute.

I'm really impressed by all the progress that has been made!

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
___

[NTG-context] wiki update - status

[Garulfo]

Hi all,

New source browser is nice ! Thanks a lot.

After level 1 (Main Page / Download and Install / Documentation / 
Mailing lists), I mostly finished a review of level 2 (and some level 3) 
pages.


Several tweaks all over the place like:

- Fonts: full update for newcomers,
- Try to be responsive "enough" for smartphone
- More homogeneous style / theme
- Old Content category and tag pages, update dead links
- Layout:
  - do the todo, like merging content of paper setup + paper sizes pages
  - complete the flow with imposition
  - rework the "Further reading section", add PDF links and so on
- Programming & DB:
  - Gather "Calling Lua from TeX" and "Calling TeX from Lua"
(section +links) in a same page
- Tools:
  - segregate "core tools" and "additional tools"
  - highlight existence of mtxrun and context scripts pages
- Remove former "manually made links bar" at the top of the pages
  current structure should be enough now have an easier understanding of
  the wiki structure.

Thanks for your help Taco, Hans, Aditya, Hraban, Tomáš.

I hope that this will help to improve the reception of users and their 
willingness to contribute.


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

Re: [NTG-context] [feature] update

[Floris van Manen]

On 09-08-19 16:18, Hans Hagen wrote:
> it uses rsync so it already does partial downloads
> 

but it is still very verbose...
is there a less-verbose switch ?

.F


pEpkey.asc
Description: application/pgp-keys
___
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
___

Re: [NTG-context] [feature] update

[Hans Hagen]

On 8/9/2019 2:32 PM, Floris van Manen wrote:

I do a daily update of the context distribution using the command
sh ./first-setup.sh --modules=all --engine=luatex

This works well, but is rather verbose on the screen.
Would it be possible to have a less verbose version?
Or that the script could check some kind of a checksum before deciding
to download all data? Or download only part of the data (saving on some
carbon footprint ;-)

it uses rsync so it already does partial downloads

(lmtx uses a different method)

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
___

[NTG-context] [feature] update

[Floris van Manen]

I do a daily update of the context distribution using the command
sh ./first-setup.sh --modules=all --engine=luatex

This works well, but is rather verbose on the screen.
Would it be possible to have a less verbose version?
Or that the script could check some kind of a checksum before deciding
to download all data? Or download only part of the data (saving on some
carbon footprint ;-)

Thanks.
.Floris





pEpkey.asc
Description: application/pgp-keys
___
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
___

[NTG-context] circuitikz update with ConTeXt fixes

[Mojca Miklavec]

Hi,

I recieved this via CTAN updates.

Any volunteers for testing?

(Using --modules=all or --modules=t-tikz should automatically give you
the latest version.)

Mojca


On Mon, 24 Jun 2019 at 12:00,  wrote:
>
> Romano Giannetti submitted an update to the
>
> circuitikz
>
> package.
>
> Version:  0.9.2 2019-06-21
> License:  lppl gpl
>
> Summary description:  Draw electrical networks with TikZ
>
> Announcement text:
> --
>
>  This is basically a bug-fix release for ConTeXt following 0.9.1.
>  Release 0.9.2 (2019-06-21)
>
>   - (hopefully) fixed ConTeXt compatibility. Most new functionality is not 
> tested;
>  testers and developers for the ConTeXt side are needed.
>   - Added old ConTeXt version for 0.8.3
>   - Added tailless ground
>
>  Release 0.9.1:
>
>- Added old LaTeX versions for 0.8.3, 0.7, 0.6 and 0.4
>- Added the option to have inline transformers and gyrators
>- Added rotary switches
>- Added more configurable bipole nodes (connectors) and more shapes
>- Added 7-segment displays
>- Added vacuum tubes by J. op den Brouw
>- Made the open shape of dcisources configurable
>- Made the arrows on vcc and vee configurable
>- Fixed anchors of diamondpole nodes
>- Fixed a bug (#205) about unstable anchors in the chip components
>- Fixed a regression in label placement for some values of scaling
>- Fixed problems with cute switches anchors
>
> --
>
> The package’s Catalogue entry can be viewed at
>https://ctan.org/pkg/circuitikz
>
> The package’s files themselves can be inspected at
>http://mirror.ctan.org/graphics/pgf/contrib/circuitikz/
___
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
___

Re: [NTG-context] Wiki update

[Hans Hagen]

On 5/30/2019 9:34 PM, Otared Kavian wrote:

On 30 May 2019, at 12:07, Taco Hoekwater  wrote:
[…]

For example,

  section

outputs a table with the formal calling convention(s) for the \section command. 
Multiple tables actually, as it also outputs the alternative calls with 
different arguments, and it outputs the definition of the internal \*section* 
command, of which \section is an instance. (The parents of instances are 
printed in a slanted font).


This is absolutely magic and extremely useful! Thank you, Wolfgang, Taco and 
Hans!

I wonder whether the magic behind the scenes would allow some day to say
\syntax[section]
within a ConTeXT document… :-)


\usemodule[setups-basics]
\loadsetups[i-context]

\starttext

\basicsetup{section:instance}

\shortsetup{section:instance}

\showsetup {section:instance}

\stoptext

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

Re: [NTG-context] Wiki update

[Otared Kavian]

> On 30 May 2019, at 12:07, Taco Hoekwater  wrote:
> […]
> 
> For example,
> 
>  section
> 
> outputs a table with the formal calling convention(s) for the \section 
> command. Multiple tables actually, as it also outputs the alternative calls 
> with different arguments, and it outputs the definition of the internal 
> \*section* command, of which \section is an instance. (The parents of 
> instances are printed in a slanted font).

This is absolutely magic and extremely useful! Thank you, Wolfgang, Taco and 
Hans!

I wonder whether the magic behind the scenes would allow some day to say
\syntax[section]
within a ConTeXT document… :-)

Best regards, and again many many thanks: OK
___
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
___

Re: [NTG-context] Wiki update

[Hans Hagen]

On 5/30/2019 12:07 PM, Taco Hoekwater wrote:


I have not auto-replaced any of the handcrafted command page syntax tables in 
the existing wiki pages, because quite often the current syntax table has 
manual additions explaining various options. In the formal version these are 
obviously not present, and I did not want to remove any of that extra 
information.


maybe at some point we can have extra xml files that explain some of 
that (after all there is a 'xml path' to such an entry ... something to 
discuss at a meeting



Anyway, the nice thing about this new wiki plugin is that if you want to create a 
page for a specific command that is not in existence right now, it is a simple matter 
of going to the expected url, and creating a page with just a Syntax heading and a 
 tag.

For example (created a minute ago):

url:
   https://wiki.contextgarden.net/Command/setupdescription

content:
   == Syntax ==

   setupdescription


Thanks go to Wolfgang for all the hard work!

And you too!

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
___

Re: [NTG-context] Wiki update

[Procházka Lukáš Ing .]

Hello Taco,


From now on, when you are editing the wiki (especially the /Command/CMD pages), you can use 
CMD to output the formal table of arguments
for that CMD (omit the backslash)

For example,

  section

outputs a table with the formal calling convention(s) for the \section command. 
Multiple tables actually, as it also outputs the alternative calls with 
different arguments, and it outputs the definition of the internal \*section* 
command, of which \section is an instance. (The parents of instances are 
printed in a slanted font).


this is really great!

This gives idea what syntax "sugars" (alternatives) are possible and what args 
may be used! This lacked for years!


===

I have not auto-replaced any of the handcrafted command page syntax tables in 
the existing wiki pages, because quite often the current syntax table has 
manual additions explaining various options. In the formal version these are 
obviously not present, and I did not want to remove any of that extra 
information.

Anyway, the nice thing about this new wiki plugin is that if you want to create a 
page for a specific command that is not in existence right now, it is a simple matter 
of going to the expected url, and creating a page with just a Syntax heading and a 
 tag.

For example (created a minute ago):

url:
  https://wiki.contextgarden.net/Command/setupdescription

content:
  == Syntax ==

  setupdescription


My suggestions is to add an auto-generated-command-syntax wiki-page-section, 
too.

I find it very useful - just now one can see what are possibilities!

I added the following code into wiki page - just for testing purposes, anyone 
can alter the page:

https://wiki.contextgarden.net/Command/section#Syntax



== [[Help:Reference|Syntax (generated automatically from ConTeXt definition)]] 
==
section



And just now I can see that \section accepts syntax of the forms:

\section[MyRef]{My title}
\section[MyRef]{4.0}{My title}
\section[reference=MyRef,ownnumber=4.0,title={My title}]

So better for us if we find a way to COMBINE command descriptions already existing on wiki 
WITH those generated via command injection.

Thanks again for the great job.

Best regards,

Lukas


Thanks go to Wolfgang for all the hard work!



Best wishes,
Taco



--
Ing. Lukáš Procházka | mailto:l...@pontex.cz
Pontex s. r. o.  | mailto:pon...@pontex.cz | http://www.pontex.cz | IDDS: 
nrpt3sn | IČO: 40763439
Bezová 1658
147 14 Praha 4

Mob.: +420 702 033 396

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

Re: [NTG-context] Wiki update

[Jan U. Hasecke]

Am 30.05.19 um 12:07 schrieb Taco Hoekwater:
> url:
>   https://wiki.contextgarden.net/Command/setupdescription
> 
> content:
>   == Syntax ==
> 
>   setupdescription

Brilliant!

Thanks a lot!

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

[NTG-context] Wiki update

[Taco Hoekwater]

Hi all,


Not sure how many of you remember this, but at the Kalenberg meeting in 2016 
there was this talk:

===
  Setups

  Wolfgang Schuster (and Hans Hagen)

  The user interface is described in xml files but the actual descriptions 
lagged behind development. Wolfgang spent a considerable amount of time to 
describe all commands in detail and we updated the descriptive format in the 
process. The rendering was partly redone, as was the help system and scripts 
that use this information.
===

Since then, nothing much had been done with those updated xml files, which is a 
big shame considering the enormous amount of work that went into the process.

But recently we have been discussing the wiki and (especially) the sorry state 
of the reference portion of that. At some point, I realised that we could 
rather easily combine the new xml interface files with a small wiki extension, 
such that the wiki has easy access to the latest and greatest command list.

===

From now on, when you are editing the wiki (especially the /Command/CMD pages), 
you can use CMD to output the formal table of arguments
for that CMD (omit the backslash)

For example,

  section

outputs a table with the formal calling convention(s) for the \section command. 
Multiple tables actually, as it also outputs the alternative calls with 
different arguments, and it outputs the definition of the internal \*section* 
command, of which \section is an instance. (The parents of instances are 
printed in a slanted font).

There are 2035 normal commands and 373 instances in the database, essentially 
covering all the style- and document-level commands in ConTeXt.
I’ve decided not to add the low-level system commands because (apart from 
perhaps a few special cases) these do not belong in general user documentation.

===

I have not auto-replaced any of the handcrafted command page syntax tables in 
the existing wiki pages, because quite often the current syntax table has 
manual additions explaining various options. In the formal version these are 
obviously not present, and I did not want to remove any of that extra 
information.  

Anyway, the nice thing about this new wiki plugin is that if you want to create 
a page for a specific command that is not in existence right now, it is a 
simple matter of going to the expected url, and creating a page with just a 
Syntax heading and a  tag. 

For example (created a minute ago):

url:
  https://wiki.contextgarden.net/Command/setupdescription

content:
  == Syntax ==

  setupdescription


Thanks go to Wolfgang for all the hard work!

Best wishes,
Taco




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

Re: [NTG-context] Standalone update hangs

[Henri]

Sorry, there was a symlink in the ConTeXt root and I guess the updater tried to 
scan it or so and
there was a circular symlink.  I deleted the link and all is well.

Sorry for the noise.

On Tue, 2018-01-02 at 22:36 +0100, Hans Hagen wrote:
> On 1/2/2018 10:27 PM, Henri wrote:
> > 
> > Dear devs,
> > 
> > I wanted to update standalone today but the update hangs at the following 
> > line with 100% CPU
> > usage
> > and growing memory consumption.
> > 
> > 
> > resolvers   | globbing | confusing filename, name: 'Autotext.xba', 
> > lower: 'autotext.xba',
> > already: 'AutoText.xba'
> > 
> > 
> > When I Ctrl+C'd out of it I saw this message.
> > 
> > 
> > /opt/context/tex/texmf-linux-64/bin/mtxrun:404: cannot open 
> > /opt/context/tex/texmf-linux-
> > 64/lib/llvm-
> > 3.8/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+
> > Asse
> > rts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+
> > Asse
> > rts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+
> > Asse
> > rts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+
> > Asse
> > rts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+
> > Asse
> > rts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Release/build/Release/buil
> > d/Re
> > lease/build/Debug+Asserts/build/Release/build/Debug+Asserts/build/Release/build/Debug+Asserts/bu
> > ild/
> > Release/build/Debug+Asserts/build/Release/lib/clang/3.8.0/include/sanitizer/:
> >  Too many levels of
> > symbolic links
> I have no clue what AutoText.xba is, it's not in the distribution is 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 / 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
___

Re: [NTG-context] Standalone update hangs

[Hans Hagen]

On 1/2/2018 10:27 PM, Henri wrote:

Dear devs,

I wanted to update standalone today but the update hangs at the following line 
with 100% CPU usage
and growing memory consumption.


resolvers   | globbing | confusing filename, name: 'Autotext.xba', lower: 
'autotext.xba',
already: 'AutoText.xba'


When I Ctrl+C'd out of it I saw this message.


/opt/context/tex/texmf-linux-64/bin/mtxrun:404: cannot open 
/opt/context/tex/texmf-linux-
64/lib/llvm-
3.8/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asse
rts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asse
rts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asse
rts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asse
rts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asse
rts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Release/build/Release/build/Re
lease/build/Debug+Asserts/build/Release/build/Debug+Asserts/build/Release/build/Debug+Asserts/build/
Release/build/Debug+Asserts/build/Release/lib/clang/3.8.0/include/sanitizer/: 
Too many levels of
symbolic links

I have no clue what AutoText.xba is, it's not in the distribution is 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 / 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
___

[NTG-context] Standalone update hangs

[Henri]

Dear devs,

I wanted to update standalone today but the update hangs at the following line 
with 100% CPU usage
and growing memory consumption.


resolvers   | globbing | confusing filename, name: 'Autotext.xba', lower: 
'autotext.xba',
already: 'AutoText.xba'


When I Ctrl+C'd out of it I saw this message.


/opt/context/tex/texmf-linux-64/bin/mtxrun:404: cannot open 
/opt/context/tex/texmf-linux-
64/lib/llvm-
3.8/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asse
rts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asse
rts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asse
rts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asse
rts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asse
rts/build/Debug+Asserts/build/Debug+Asserts/build/Debug+Asserts/build/Release/build/Release/build/Re
lease/build/Debug+Asserts/build/Release/build/Debug+Asserts/build/Release/build/Debug+Asserts/build/
Release/build/Debug+Asserts/build/Release/lib/clang/3.8.0/include/sanitizer/: 
Too many levels of
symbolic links


Please fix.
Cheers,
Henri
___
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
___

Re: [NTG-context] Module Update from GIT URL Fails

[Christoph Reller]

On Wed, 27 Sep 2017 11:55:06 +0200 Taco Hoekwater 
wrote:

>
> Alright, I think I have this figured out now. You *have to* use the https
> protocol, but then it should work.
>
>https://bitbucket.org/philexander/context-highlight.git
>
> You cannot use any git protocol except (anonymous) https. If you try
> any other protocol, the 'git clone' command that is started by the
> webserver
> will attempt to do an interactive input query and subsequently fail.
>
> I have updated help.html with the above explanation as well.
>
> Best wishes,
> Taco
>

Thank you Taco!

With the https protocol the upload of a new version indeed works. Thank you
also for updating the help page.

Regards,
Christoph
___
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
___

Re: [NTG-context] Module Update from GIT URL Fails

[Taco Hoekwater]

Hi,

Alright, I think I have this figured out now. You *have to* use the https
protocol, but then it should work. 

   https://bitbucket.org/philexander/context-highlight.git

You cannot use any git protocol except (anonymous) https. If you try
any other protocol, the 'git clone' command that is started by the webserver
will attempt to do an interactive input query and subsequently fail.

I have updated help.html with the above explanation as well.

Best wishes,
Taco


> On 26 Sep 2017, at 11:51, Christoph Reller  wrote:
> 
> Thank you for your effort. Unfortunately, I still get the same error "Change 
> to temporary directory failed". Could you please be so kind and check once 
> more what could be wrong with the server. 
> 


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

Re: [NTG-context] Module Update from GIT URL Fails

[Christoph Reller]

On Mon, 25 Sep 2017 10:57:48 +0200 Taco Hoekwater  wrote:

> > I don't seem to be able to update my ConTeXt module "high". I try to
> create a new version by entering the URL of my git repository
> (g...@bitbucket.org:philexander/context-highlight.git) into the GIT URL
> field and clicking submit. But the website then tells me "Change to
> temporary directory failed". What am I doing wrong?
>
> Not you, me. Something was wrong with the directory permissions on the
> server. It should
> be fixed now, but I cannot test myself. Please let me know whether it
> works ok now.
>

Dear Taco,

Thank you for your effort. Unfortunately, I still get the same error
"Change to temporary directory failed". Could you please be so kind and
check once more what could be wrong with the server.

On Mon, 25 Sep 2017 21:01:18 -0400 (EDT) Aditya Mahajan  wrote:

> > I try to create
> > a new version by entering the URL of my git repository
> > (g...@bitbucket.org:philexander/context-highlight.git)
> > into the GIT URL field
>
> OT: Since you haven't uploaded your module yet, might I suggest that you
> change the name to t-highlight instead of t-high. That will be in line
> with the ConTeXt convention of using full names instead of abbreviations.
>
> Thanks,
> Aditya
>

 Thank you for this hint, Aditya. I have renamed the module and am awaiting
that the Update from GIT URL works again.

Kind regards to both of you,

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

Re: [NTG-context] Module Update from GIT URL Fails

[Aditya Mahajan]

I try to create
a new version by entering the URL of my git repository
(g...@bitbucket.org:philexander/context-highlight.git)
into the GIT URL field


OT: Since you haven't uploaded your module yet, might I suggest that you 
change the name to t-highlight instead of t-high. That will be in line 
with the ConTeXt convention of using full names instead of abbreviations.


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

Re: [NTG-context] Module Update from GIT URL Fails

[Taco Hoekwater]

Hello Christoph,

> On 22 Sep 2017, at 09:20, Christoph Reller  wrote:
> 
> Dear Taco,
> 
> Moica has told me that you are the maintainer of modules.contextgarden.net. 
> Is this correct?

Yes, that is correct.

> I don't seem to be able to update my ConTeXt module "high". I try to create a 
> new version by entering the URL of my git repository 
> (g...@bitbucket.org:philexander/context-highlight.git) into the GIT URL field 
> and clicking submit. But the website then tells me "Change to temporary 
> directory failed". What am I doing wrong?

Not you, me. Something was wrong with the directory permissions on the server. 
It should
be fixed now, but I cannot test myself. Please let me know whether it works ok 
now.

> By the way: My web browser tells me that the certificate of 
> https://modules.contextgarden.net has expired.

I am aware. Something is going wrong with the auto-renewal of the certificate.

Best wishes,
Taco



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

[NTG-context] Module Update from GIT URL Fails

[Christoph Reller]

Dear Taco,

Moica has told me that you are the maintainer of modules.contextgarden.net.
Is this correct?

I don't seem to be able to update my ConTeXt module "high". I try to create
a new version by entering the URL of my git repository
(g...@bitbucket.org:philexander/context-highlight.git)
into the GIT URL field and clicking submit. But the website then tells me
"Change to temporary directory failed". What am I doing wrong?

By the way: My web browser tells me that the certificate of
https://modules.contextgarden.net has expired.

Kind regards,
Christoph
___
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
___

Re: [NTG-context] cannot update to latest beta

[Philipp Gesang]

·

> On Wed, 12 Oct 2016, Philipp Gesang wrote:
> 
> > It seems fixed now and the most recent commit does indeed have
> > Hans as the author.
> 
> FYI, I have been mirroring your repo to github:
> https://github.com/contextgarden/context-mirror
> 
> If you want, I can give you push access to the github repo and you could 
> push to both bitbucket and github at the same time. Otherwise, I can 
> continue to run a script locally that does the mirroring.

Thanks for the offer but I prefer to keep it as it is. The
star-like topology with a central mirror being pushed to by the
bot and others pulling from it is clean and simple. I’m doing the
same btw. with my cgit mirror https://git.phi-gamma.net/ConTeXt/
which runs on the same server but is completely isolated from the
mirror. (Don’t pull from that one though, it’ll kill my
bandwidth.)

In any case Bitbucket is as reliable as any hoster and in my
experience a good deal less infuriating maintenance wise than
Github.

Best,
Philipp



pgppBhO7SXteh.pgp
Description: PGP signature
___
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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] cannot update to latest beta

[Aditya Mahajan]

Hi Philipp,

On Wed, 12 Oct 2016, Philipp Gesang wrote:


It seems fixed now and the most recent commit does indeed have
Hans as the author.


FYI, I have been mirroring your repo to github:
https://github.com/contextgarden/context-mirror

If you want, I can give you push access to the github repo and you could 
push to both bitbucket and github at the same time. Otherwise, I can 
continue to run a script locally that does the mirroring.


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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] cannot update to latest beta

[Philipp Gesang]

Hey Mohammad,

thanks for your message!

·
> The bitbucket mirror has not gotten updated since September 24.  Is there a
> misconfiguration?

Sort of. I changed the bot after talking to Mojca at Kalenberg to
include Hans as the commit author in order to facilitate the
merging of various repo archives at some point in the future. It
seems though that I messed up parts of the code in the process
and disregarded the notification emails the bot was kept sending
me due to failed commits. Oh my.

It seems fixed now and the most recent commit does indeed have
Hans as the author.

Best,
Philipp





pgpUqGcyxOloZ.pgp
Description: PGP signature
___
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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] cannot update to latest beta

[Mohammad Hossein Bateni]

Phillip,

The bitbucket mirror has not gotten updated since September 24.  Is there a
misconfiguration?

—MHB

On Thu, Sep 22, 2016 at 4:01 PM, Taco Hoekwater  wrote:

> Hi Pablo,
>
> > Op 22 sep. 2016 om 20:53 heeft Pablo Rodriguez  het
> volgende geschreven:
> >
> >> On 09/21/2016 11:26 PM, Philipp Gesang wrote:
> >> ·
> >>
> >>> Dear list,
> >>>
> >>> although latest beta seems to be from 2016.09.20 21:12, I get updated
> to
> >>> beta from 2016.09.12 18:27 when I run:
> >>
> >> The official download still has the 2016.09.12 timestamp:
> >> http://pragma-ade.nl/download-2.htm How did you get that other
> >> date? I hope the git mirror isn’t scraping the wrong page ;)
> >
> > Philipp,
> >
> > I know that there is a new beta reading the metadata from
> > http://www.pragma-ade.com/general/qrcs/setup-en.pdf.
> >
> > Here is the revealing field:
> >
> >Creator:ConTeXt - 2016.09.22 10:48
>
> True, this means there exists a new version of context somewhere. But what
> you do not know is that there is a third context release state. Besides
> 'current' and 'beta' there is also 'latest'.
>
> 'Latest' contains experimental and/or in development code that needs to be
> shared for further testing or development. The easiest way for Hans to do
> that is to upload a new version to the website, and whenever any version of
> context is uploaded, the qrcs are uploaded as well.
>
> An easier and safer way to check for a new context release is to browse
> through the 'download' section of the Pragma website, which is always
> auto-updated in the release process. Or just run first-setup whenever you
> feel like it ;)
>
> Best wishes,
> Taco
>
>
> >
> > When a new beta is realeased, this is the easiest way for me to know.
> >
> > But probably Hans is busy with the ConTeXt Meeting next week and he
> > didn’t upload the beta.
> >
> > Many thanks for your help,
> >
> > 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://tex.aanhet.net
> > archive  : http://foundry.supelec.fr/projects/contextrev/
> > 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://tex.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> 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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] modules.contextgarden.net update

[Wolfgang Schuster]

Hi Taco,

can you send me a temporary password.

Kind regards,
Wolfgang

Taco Hoekwater 
10. Oktober 2016 um 15:46
Hi,

Some of you will know already that the module author section of

https://modules.contextgarden.net

is functional again, as presented at the ConTeXt meeting last month.

However, nobody can log in, because module authors now have a password
(no more automatic wiki-connect). For new module authors, the registration
process will handle the setup of password and such, but legacy authors
need manual intervention.

So, if you are the current maintainer of a module on modules.cg.net,
please drop me an email message so I can hand you a temporary password 
for

logging on (the old wiki-connect code did not store e-mail addresses
either, making it hard to reach everyone except via this list).

It would be good if the current authors could update their module
metadata(s), because the new code has support for a “works with 
mkii/mkiv”

flag as well as some other new fields. Also, I welcome comments and
feature requests, now that the website code is in a language I can
easily program in.

Once most of the modules have been updated to reflect their mkii/mkiv
state, I can start designing a search/filter interface to improve the
front-end of the site.

Best wishes,
Taco



___
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
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  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] modules.contextgarden.net update

[Taco Hoekwater]

Hi,

Some of you will know already that the module author section of 

  https://modules.contextgarden.net 

is functional again, as presented at the ConTeXt meeting last month. 

However, nobody can log in, because module authors now have a password 
(no more automatic wiki-connect). For new module authors, the registration
process will handle the setup of password and such, but legacy authors 
need manual intervention.
 
So, if you are the current maintainer of a module on modules.cg.net,
please drop me an email message so I can hand you a temporary password for 
logging on (the old wiki-connect code did not store e-mail addresses
either, making it hard to reach everyone except via this list).

It would be good if the current authors could update their module
metadata(s), because the new code has support for a “works with mkii/mkiv” 
flag as well as some other new fields. Also, I welcome comments and
feature requests, now that the website code is in a language I can 
easily program in.

Once most of the modules have been updated to reflect their mkii/mkiv 
state, I can start designing a search/filter interface to improve the
front-end of the site.

Best wishes,
Taco



___
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] cannot update to latest beta

[Taco Hoekwater]

Hi Pablo,

> Op 22 sep. 2016 om 20:53 heeft Pablo Rodriguez  het volgende 
> geschreven:
> 
>> On 09/21/2016 11:26 PM, Philipp Gesang wrote:
>> ·
>> 
>>> Dear list,
>>> 
>>> although latest beta seems to be from 2016.09.20 21:12, I get updated to
>>> beta from 2016.09.12 18:27 when I run:
>> 
>> The official download still has the 2016.09.12 timestamp:
>> http://pragma-ade.nl/download-2.htm How did you get that other
>> date? I hope the git mirror isn’t scraping the wrong page ;)
> 
> Philipp,
> 
> I know that there is a new beta reading the metadata from
> http://www.pragma-ade.com/general/qrcs/setup-en.pdf.
> 
> Here is the revealing field:
> 
>Creator:ConTeXt - 2016.09.22 10:48

True, this means there exists a new version of context somewhere. But what you 
do not know is that there is a third context release state. Besides 'current' 
and 'beta' there is also 'latest'. 

'Latest' contains experimental and/or in development code that needs to be 
shared for further testing or development. The easiest way for Hans to do that 
is to upload a new version to the website, and whenever any version of context 
is uploaded, the qrcs are uploaded as well.

An easier and safer way to check for a new context release is to browse through 
the 'download' section of the Pragma website, which is always auto-updated in 
the release process. Or just run first-setup whenever you feel like it ;)

Best wishes,
Taco


> 
> When a new beta is realeased, this is the easiest way for me to know.
> 
> But probably Hans is busy with the ConTeXt Meeting next week and he
> didn’t upload the beta.
> 
> Many thanks for your help,
> 
> 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://tex.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] cannot update to latest beta

[Pablo Rodriguez]

On 09/21/2016 11:26 PM, Philipp Gesang wrote:
> ·
> 
>> Dear list,
>>
>> although latest beta seems to be from 2016.09.20 21:12, I get updated to
>> beta from 2016.09.12 18:27 when I run:
> 
> The official download still has the 2016.09.12 timestamp:
> http://pragma-ade.nl/download-2.htm How did you get that other
> date? I hope the git mirror isn’t scraping the wrong page ;)

Philipp,

I know that there is a new beta reading the metadata from
http://www.pragma-ade.com/general/qrcs/setup-en.pdf.

Here is the revealing field:

Creator:ConTeXt - 2016.09.22 10:48

When a new beta is realeased, this is the easiest way for me to know.

But probably Hans is busy with the ConTeXt Meeting next week and he
didn’t upload the beta.

Many thanks for your help,

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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] cannot update to latest beta

[Philipp Gesang]

·

> Dear list,
> 
> although latest beta seems to be from 2016.09.20 21:12, I get updated to
> beta from 2016.09.12 18:27 when I run:

The official download still has the 2016.09.12 timestamp:
http://pragma-ade.nl/download-2.htm How did you get that other
date? I hope the git mirror isn’t scraping the wrong page ;)

Best,
Philipp



pgpfUxP2j0Sn1.pgp
Description: PGP signature
___
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] cannot update to latest beta

[Pablo Rodriguez]

Dear list,

although latest beta seems to be from 2016.09.20 21:12, I get updated to
beta from 2016.09.12 18:27 when I run:

   rsync -ptv rsync://contextgarden.net/minimals/setup/first-setup.sh .
   ./first-setup.sh --modules=all

Just in case it makes sense,

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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] ConTeXt update issue

[Hans Hagen]

On 1/7/2016 5:35 PM, kle...@sxmail.de wrote:

Dear list,

I have experienced a problem updating the ConTeXt version I use on a
current Linux operating system flavour beginning ca. two months ago.
By that time, as was successfully applied several times before within
the past year of me using ConTeXt, I initiated the update process on the
bash console via one command recommended on the corresponding ConTeXt
page: "sh ./first-setup.sh --context=current".
Then, and on two other ocassions very recently, ConTeXt got stuck (after
data had indeed been received and some actions concerning the usual
update had been executed, too) giving back the following lines in the
bash console that puzzled me a lot:
"...
This is LuaTeX, Version beta-0.87.0 (TeX Live 2016/dev)  (INITEX)
  system commands enabled.
(/home/ichha lt/context/tex/texmf-context/tex/context/base/cont-nl.mkiv
(/home/ichhalt/context/tex/texmf-context/tex/context/base/context.mkiv(/home/ichhalt/context/tex/texmf-context/tex/context/base/syst-ini.mkiv
! Undefined control sequence.
l.1020 pdfoutput
  zerocount"
I admit that this code example is quite short, but it is definitely the
last that the whole ConTeXt update process returns-otherwise it stood still.
What-except for uninstalling and re-installing ConTeXt-could help now?
If ever possible, a conservation of my current ConTeXt installation
appeared preferable to me.
Thank you in advance.


this points to a mismatch in tex files and luatex ... you need to 
install the context beta as the older current doesn't work with the new 
luatex binary


Hans



-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
 | 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] cannot update latest beta

[Pablo Rodriguez]

Dear list,

I have just tried to update ConTeXt to latest beta (as many times
before) with rsync -ptv
rsync://contextgarden.net/minimals/setup/first-setup.sh . and I got the
following error message:

rsync: failed to connect to contextgarden.net (193.2.4.200): No route to
host (113)
rsync error: error in socket IO (code 10) at clientserver.c(128)
[Receiver=3.1.0pre1]

Is anyone experiencing the same error?

Many thanks for your help,


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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] cannot update latest beta

[Mojca Miklavec]

On Sun, Dec 22, 2013 at 9:40 PM, Pablo Rodriguez wrote:
 Dear list,

 I have just tried to update ConTeXt to latest beta (as many times
 before) with rsync -ptv
 rsync://contextgarden.net/minimals/setup/first-setup.sh . and I got the
 following error message:

 rsync: failed to connect to contextgarden.net (193.2.4.200): No route to
 host (113)
 rsync error: error in socket IO (code 10) at clientserver.c(128)
 [Receiver=3.1.0pre1]

 Is anyone experiencing the same error?

The admin is doing some major software upgrade and the machine is down
at the moment. (He told me he would do it sometime soon, but he didn't
mention when.)

I'm sorry for the inconvenience. I wasn't aware of the upgrade either
until you asked, but I hope that it won't take too long.

There are two mirrors, I only need to find the address. (Taco's server
had some issues with rsync in the last few days, but there must be
Hans' mirror available as well.)

Mojca
___
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] cannot update latest beta

[Mojca Miklavec]

On Mon, Dec 23, 2013 at 12:07 AM, Mojca Miklavec wrote:
 On Sun, Dec 22, 2013 at 9:40 PM, Pablo Rodriguez wrote:
 Dear list,

 I have just tried to update ConTeXt to latest beta (as many times
 before) with rsync -ptv
 rsync://contextgarden.net/minimals/setup/first-setup.sh . and I got the
 following error message:

 rsync: failed to connect to contextgarden.net (193.2.4.200): No route to
 host (113)
 rsync error: error in socket IO (code 10) at clientserver.c(128)
 [Receiver=3.1.0pre1]

 Is anyone experiencing the same error?

 The admin is doing some major software upgrade and the machine is down
 at the moment. (He told me he would do it sometime soon, but he didn't
 mention when.)

 I'm sorry for the inconvenience. I wasn't aware of the upgrade either
 until you asked, but I hope that it won't take too long.

The machine is up again.

Mojca
___
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___