> On 11. Jul 2017, at 17:09, Hans Hagen <pra...@wxs.nl> wrote:
>
> On 7/11/2017 4:36 PM, Thomas Floeren wrote:
>>> On 4. Jun 2017, at 18:55, Hans Hagen <pra...@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___________________________________________________________________________________
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
___________________________________________________________________________________
