synctex

synctex

[Patrick Gundlach]

Hi,

I don't know if this has been discussed before: is there a working
setup with synctex? All I get a pointer to \stoptext when I click on
any position in the PDF file. Any magick to do?

Patrick
-- 
ConTeXt wiki and more: 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

synctex

[Vyatcheslav Yatskovsky]

Hi,

I have a discussion with Jonathan Kew  about mark IV option in TeXWorks.

We need to to pass the argument "-synctex=1" to the actual *tex 
invocation, so that the engine creates a .synctex.gz file alongside the 
.pdf output; this enables texworks to jump back and forth between source 
and preview locations.

How this can be done?

Regards,
Vyatcheslav
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: synctex

[Hans Hagen]

Vyatcheslav Yatskovsky wrote:
> Hi,
> 
> I have a discussion with Jonathan Kew  about mark IV option in TeXWorks.
> 
> We need to to pass the argument "-synctex=1" to the actual *tex 
> invocation, so that the engine creates a .synctex.gz file alongside the 
> ..pdf output; this enables texworks to jump back and forth between 
> source and preview locations.
> 
> How this can be done?

\synctex=1

as it's not something that you want to have on by default

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: synctex

[Wolfgang Schuster]

Am 12.09.2009 um 13:22 schrieb Hans Hagen:

> Vyatcheslav Yatskovsky wrote:
>> Hi,
>> I have a discussion with Jonathan Kew  about mark IV option in  
>> TeXWorks.
>> We need to to pass the argument "-synctex=1" to the actual *tex  
>> invocation, so that the engine creates a .synctex.gz file alongside  
>> the ..pdf output; this enables texworks to jump back and forth  
>> between source and preview locations.
>> How this can be done?
>
> \synctex=1
>
> as it's not something that you want to have on by default

is a parameter for the context command (context --synctex filename)  
not a option?

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

Re: synctex

[Hans Hagen]

Wolfgang Schuster wrote:
> 
> Am 12.09.2009 um 13:22 schrieb Hans Hagen:
> 
>> Vyatcheslav Yatskovsky wrote:
>>> Hi,
>>> I have a discussion with Jonathan Kew  about mark IV option in TeXWorks.
>>> We need to to pass the argument "-synctex=1" to the actual *tex 
>>> invocation, so that the engine creates a .synctex.gz file alongside 
>>> the ..pdf output; this enables texworks to jump back and forth 
>>> between source and preview locations.
>>> How this can be done?
>>
>> \synctex=1
>>
>> as it's not something that you want to have on by default
> 
> is a parameter for the context command (context --synctex filename) not 
> a option?

this had been considered but i then fear that editors will be set up by 
default to use that switch which is not what i've in mind; in that case 
the editor should have a config option either of not to enable that flag

so .. i haven't made up my mind yet

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: synctex

[Hartmut Henkel]

On Sat, 12 Sep 2009, Hans Hagen wrote:
> Vyatcheslav Yatskovsky wrote:
> >
> > I have a discussion with Jonathan Kew about mark IV option in
> > TeXWorks.
> >
> > We need to to pass the argument "-synctex=1" to the actual *tex
> > invocation, so that the engine creates a .synctex.gz file alongside
> > the ..pdf output; this enables texworks to jump back and forth
> > between source and preview locations.
> >
> > How this can be done?
>
> \synctex=1
>
> as it's not something that you want to have on by default

...and afaics it doesn't work multidir, as synctex doesn't know about
directions (yet). So currently there is not much practical use for
synctex in luatex.

Regards, Hartmut
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: synctex

[Mojca Miklavec]

On Sun, Sep 13, 2009 at 02:18, Hartmut Henkel wrote:
>
> ...and afaics it doesn't work multidir, as synctex doesn't know about
> directions (yet). So currently there is not much practical use for
> synctex in luatex.

Unless one uses left-to-right/top-to-bottom text direction :)

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

Re: synctex

[Hans Hagen]

Hartmut Henkel wrote:
> On Sat, 12 Sep 2009, Hans Hagen wrote:
>> Vyatcheslav Yatskovsky wrote:
>>> I have a discussion with Jonathan Kew about mark IV option in
>>> TeXWorks.
>>>
>>> We need to to pass the argument "-synctex=1" to the actual *tex
>>> invocation, so that the engine creates a .synctex.gz file alongside
>>> the ..pdf output; this enables texworks to jump back and forth
>>> between source and preview locations.
>>>
>>> How this can be done?
>> \synctex=1
>>
>> as it's not something that you want to have on by default
> 
> ....and afaics it doesn't work multidir, as synctex doesn't know about
> directions (yet). So currently there is not much practical use for
> synctex in luatex.

also, in order to make it useful (in my cases) it has to be hooked into 
the error report mechanism (esp as we often deal with typeset content 
not originating in the line reported).

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

SyncTeX

[Trond Thorbjørnsen]

Is MKIV still not working with SyncTeX?

http://wiki.contextgarden.net/SyncTeX

--
Trond Thorbjørnsen
___________________________________________________________________________________
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: SyncTeX

[Mojca Miklavec]

On Tue, Jun 3, 2014 at 11:44 AM, Trond Thorbjørnsen wrote:
> Is MKIV still not working with SyncTeX?
>
> http://wiki.contextgarden.net/SyncTeX

Using:
    context --synctex filename.tex
works for me.

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: SyncTeX

[Trond Thorbjørnsen]

Hei Mojca,

Mojca Miklavec skrev 03.06.2014:
> On Tue, Jun 3, 2014 at 11:44 AM, Trond Thorbjørnsen wrote: 
> > Is MKIV still not working with SyncTeX? 
> > 
> > http://wiki.contextgarden.net/SyncTeX 
> 
> Using: 
> context --synctex filename.tex 
> works for me. 

Thank you for the reply, that was what I thought. Then it is probably
only my view settings in emacs that is wrong.

(And the sentence "SyncTeX currently does not work with MKIV." should
probably be removed from wiki.contextgarden :) )

-Trond

> 
> Mojca 
> ___________________________________________________________________________________ 
> If your question is of interest to others as well, please add an entry to the Wiki! 
> 
> maillist : ntg-context@ntg.nl / https://heim.ifi.uio.no/trondth/.t/pm06Gceaq3.php (..)ntg.nl(..) 
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net 
> archive : https://heim.ifi.uio.no/trondth/.t/Xo1s69g0pG.php (..)foundry.supelec.fr(..) 
> 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
___________________________________________________________________________________

synctex

[Hans Hagen]

Hi,

For those using synctex, an alternative method is:

\setupsynctex[state=start]

It is tuned for use in a more complex setup where one wants access to 
source files (with content) and not to e.g. styles in a tex tree. It 
also works reasonable well with (also included) xml files. Personally I 
never use synctex but for some projects it came in handy for authors 
(think of proofing xml files with hundreds of nested inclusions and 
files in a rather branched tree.) Of course you can expect a similar 
performance hit as normal synctex but commenting the above line in 
production results in zero overhead. Using the syntex flag on the 
command line (--synctex=context will work) can be messy.

This currently only works with the windows binaries version on the 
garden (as we need luatex 1.0.5).

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: synctex

[Thomas Floeren]

> On 4. Jun 2017, at 18:55, Hans Hagen <pragma@wxs.nl> wrote:
> 
> Hi,
> 
> For those using synctex, an alternative method is:
> 
> \setupsynctex[state=start]
> 
> It is tuned for use in a more complex setup where one wants access to source files (with content) and not to e.g. styles in a tex tree. It also works reasonable well with (also included) xml files. Personally I never use synctex but for some projects it came in handy for authors (think of proofing xml files with hundreds of nested inclusions and files in a rather branched tree.) Of course you can expect a similar performance hit as normal synctex but commenting the above line in production results in zero overhead. Using the syntex flag on the command line (--synctex=context will work) can be messy.
> 
> This currently only works with the windows binaries version on the garden (as we need luatex 1.0.5).

Hans, thanks for that info.

\setupsynctex[state=start] seems to work fine with Beta 2017.07.05 23:01 - LuaTeX 1.05.0 on the Mac.

Whereas I noticed that -the switches -synctex=context or --synctex=zipped have completely stopped working with that Beta (or that luatex version).

It throws errors like this on every file I've tested:

lua error       > lua error on line 33 in file ../c-000-s3-e6-front-de.tex:

...eta/tex/texmf-context/tex/context/base/mkiv/node-syn.lua:490: attempt to call upvalue 'collect' (a nil value)
stack traceback:
	...eta/tex/texmf-context/tex/context/base/mkiv/node-syn.lua:490: in function 'luatex_synctex_collect'
	[string "local nodes_references_handler = nodes.refere..."]:14: in function <[string "local nodes_references_handler = nodes.refere..."]:7>
	(...tail calls...)
	...eta/tex/texmf-context/tex/context/base/mkiv/pack-obj.lua:129: in function <...eta/tex/texmf-context/tex/context/base/mkiv/pack-obj.lua:127>
	(...tail calls...)


So, I guess it is safe to assume that the synctex command line switch is finally deprecated?

-- 
Tom
___________________________________________________________________________________
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: synctex

[Hans Hagen]

On 7/11/2017 4:36 PM, Thomas Floeren wrote:
> 
>> On 4. Jun 2017, at 18:55, Hans Hagen <pragma@wxs.nl> wrote:
>>
>> Hi,
>>
>> For those using synctex, an alternative method is:
>>
>> \setupsynctex[state=start]
>>
>> It is tuned for use in a more complex setup where one wants access to source files (with content) and not to e.g. styles in a tex tree. It also works reasonable well with (also included) xml files. Personally I never use synctex but for some projects it came in handy for authors (think of proofing xml files with hundreds of nested inclusions and files in a rather branched tree.) Of course you can expect a similar performance hit as normal synctex but commenting the above line in production results in zero overhead. Using the syntex flag on the command line (--synctex=context will work) can be messy.
>>
>> This currently only works with the windows binaries version on the garden (as we need luatex 1.0.5).
> 
> Hans, thanks for that info.
> 
> \setupsynctex[state=start] seems to work fine with Beta 2017.07.05 23:01 - LuaTeX 1.05.0 on the Mac.
> 
> Whereas I noticed that -the switches -synctex=context or --synctex=zipped have completely stopped working with that Beta (or that luatex version).

i'll have to upload a new beta ... last week i optimized the code a bit 
so performance is now a bit better too; there are some options you can 
play with to see what happens deep down

% \setupsynctex[state=start,method=min]
% \setupsynctex[state=start,method=max]
% \enabletrackers[system.synctex.visualize]
% \enabletrackers[system.synctex.visualize=real]

indeed, we now have a context specific variant only (you can still force 
the original synctex by setting \normalsynctex but it can interfere with 
the context variant when set)

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: synctex

[Thomas Floeren]

[-- Attachment #1.1: Type: text/plain, Size: 3108 bytes --]


> On 11. Jul 2017, at 17:09, Hans Hagen <pragma@wxs.nl> wrote:
> 
> On 7/11/2017 4:36 PM, Thomas Floeren wrote:
>>> On 4. Jun 2017, at 18:55, Hans Hagen <pragma@wxs.nl> wrote:
>>> 
>>> Hi,
>>> 
>>> For those using synctex, an alternative method is:
>>> 
>>> \setupsynctex[state=start]
>>> 
>>> It is tuned for use in a more complex setup where one wants access to source files (with content) and not to e.g. styles in a tex tree. It also works reasonable well with (also included) xml files. Personally I never use synctex but for some projects it came in handy for authors (think of proofing xml files with hundreds of nested inclusions and files in a rather branched tree.) Of course you can expect a similar performance hit as normal synctex but commenting the above line in production results in zero overhead. Using the syntex flag on the command line (--synctex=context will work) can be messy.
>>> 
>>> This currently only works with the windows binaries version on the garden (as we need luatex 1.0.5).
>> Hans, thanks for that info.
>> \setupsynctex[state=start] seems to work fine with Beta 2017.07.05 23:01 - LuaTeX 1.05.0 on the Mac.
>> Whereas I noticed that -the switches -synctex=context or --synctex=zipped have completely stopped working with that Beta (or that luatex version).
> 
> i'll have to upload a new beta ... last week i optimized the code a bit so performance is now a bit better too; there are some options you can play with to see what happens deep down
> 
> % \setupsynctex[state=start,method=min]
> % \setupsynctex[state=start,method=max]
> % \enabletrackers[system.synctex.visualize]
> % \enabletrackers[system.synctex.visualize=real]
> 
> indeed, we now have a context specific variant only (you can still force the original synctex by setting \normalsynctex but it can interfere with the context variant when set)


I think I have found a problem with the new synctex:

Synctex works perfectly fine – until the first occurence of a \readfile. From that point on it always takes me to the imported file, no matter whether the text actually is in the imported file or in the main file.

Here is a MWE:

\setupsynctex[state=start,method=max]
\starttext
This line is found by the new synctex.\crlf
This line is found by the new synctex.\crlf
This line is found by the new synctex.\crlf
This line is found by the new synctex.\crlf
\readfile{myInputfile}{}{}
This line is {\em not} found by the new synctex.\crlf
Instead, synctex takes me to myInputfile.tex.\crlf
This line is {\em not} found by the new synctex.\crlf
Instead, synctex takes me to myInputfile.tex.\crlf
\stoptext

['myInputfile.tex' can contain any text, it doesn't matter.]

If I click one of the first four lines in the PDF synctex works fine. The lines after the \readfile don't work: Synctex takes me to the end of myInputfile.tex. (You can also import 'ward' or 'knuth', in that case synctex takes me to the last line _before_ the \readfile.)

I tested the sample with an older Ctx and with --synctex=zipped, and it doesn't show the problem.

-- 
Tom

[-- Attachment #1.2: Type: text/html, Size: 9714 bytes --]

[-- Attachment #2: Type: text/plain, Size: 492 bytes --]

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

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: synctex

[Thomas Floeren]

[-- Attachment #1.1: Type: text/plain, Size: 4113 bytes --]


> On 11. Jul 2017, at 23:06, Thomas Floeren <thfl@mac.com> wrote:
> 
>> 
>> On 11. Jul 2017, at 17:09, Hans Hagen <pragma@wxs.nl <mailto:pragma@wxs.nl>> wrote:
>> 
>> On 7/11/2017 4:36 PM, Thomas Floeren wrote:
>>>> On 4. Jun 2017, at 18:55, Hans Hagen <pragma@wxs.nl <mailto:pragma@wxs.nl>> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> For those using synctex, an alternative method is:
>>>> 
>>>> \setupsynctex[state=start]
>>>> 
>>>> It is tuned for use in a more complex setup where one wants access to source files (with content) and not to e.g. styles in a tex tree. It also works reasonable well with (also included) xml files. Personally I never use synctex but for some projects it came in handy for authors (think of proofing xml files with hundreds of nested inclusions and files in a rather branched tree.) Of course you can expect a similar performance hit as normal synctex but commenting the above line in production results in zero overhead. Using the syntex flag on the command line (--synctex=context will work) can be messy.
>>>> 
>>>> This currently only works with the windows binaries version on the garden (as we need luatex 1.0.5).
>>> Hans, thanks for that info.
>>> \setupsynctex[state=start] seems to work fine with Beta 2017.07.05 23:01 - LuaTeX 1.05.0 on the Mac.
>>> Whereas I noticed that -the switches -synctex=context or --synctex=zipped have completely stopped working with that Beta (or that luatex version).
>> 
>> i'll have to upload a new beta ... last week i optimized the code a bit so performance is now a bit better too; there are some options you can play with to see what happens deep down
>> 
>> % \setupsynctex[state=start,method=min]
>> % \setupsynctex[state=start,method=max]
>> % \enabletrackers[system.synctex.visualize]
>> % \enabletrackers[system.synctex.visualize=real]
>> 
>> indeed, we now have a context specific variant only (you can still force the original synctex by setting \normalsynctex but it can interfere with the context variant when set)
> 
> 
> I think I have found a problem with the new synctex:
> 
> Synctex works perfectly fine – until the first occurence of a \readfile. From that point on it always takes me to the imported file, no matter whether the text actually is in the imported file or in the main file.
> 
> Here is a MWE:
> 
> \setupsynctex[state=start,method=max]
> \starttext
> This line is found by the new synctex.\crlf
> This line is found by the new synctex.\crlf
> This line is found by the new synctex.\crlf
> This line is found by the new synctex.\crlf
> \readfile{myInputfile}{}{}
> This line is {\em not} found by the new synctex.\crlf
> Instead, synctex takes me to myInputfile.tex.\crlf
> This line is {\em not} found by the new synctex.\crlf
> Instead, synctex takes me to myInputfile.tex.\crlf
> \stoptext
> 
> ['myInputfile.tex' can contain any text, it doesn't matter.]
> 
> If I click one of the first four lines in the PDF synctex works fine. The lines after the \readfile don't work: Synctex takes me to the end of myInputfile.tex. (You can also import 'ward' or 'knuth', in that case synctex takes me to the last line _before_ the \readfile.)

With 2017.07.17 00:20 the issue seems to persist.

Tom


> 
> I tested the sample with an older Ctx and with --synctex=zipped, and it doesn't show the problem.
> 
> -- 
> Tom
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl <mailto:ntg-context@ntg.nl> / http://www.ntg.nl/mailman/listinfo/ntg-context <http://www.ntg.nl/mailman/listinfo/ntg-context>
> webpage  : http://www.pragma-ade.nl <http://www.pragma-ade.nl/> / http://context.aanhet.net <http://context.aanhet.net/>
> archive  : https://bitbucket.org/phg/context-mirror/commits/ <https://bitbucket.org/phg/context-mirror/commits/>
> wiki     : http://contextgarden.net <http://contextgarden.net/>
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 19348 bytes --]

[-- Attachment #2: Type: text/plain, Size: 492 bytes --]

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

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________