![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
On 11/22/2017 9:25 AM, Ulrike Fischer wrote:
Am Tue, 21 Nov 2017 16:43:53 +0100 schrieb Hans Hagen:
ok, we have a fix for that (but it doesn't explain why context generated files make texshop unhappy)
Well I don't have a mac and texshop. And I don't have a viewer with the newest synctex parser (sumatra is from 2016).
But the synctex output of context is wrong in certain places. E.g. when I compile this:
\starttext
\input knuth
\stoptext
then the synctex file contains no reference to knuth.tex:
SyncTeX Version:1 Input:1:G:/Z-Test/test-utf8.tex Output:pdf
and synchronization fails in sumatra for me too. \ReadFile doesn't work either. actually that is correct: in context we protect files that are in the official tex tree as it's generally a bad idea if someone patches these (there is no distinction here between a style and a sample file); also, content that originates from styles and/or is generated on the fly makes no sense for editing anyway so page ornaments are also not synced
\enabletrackers[system.synctex.visualize] will show you what is synced on the other hand, we do support (for as far as possible) xml nodes which can be flushed in arbitrary order (it's why i added support: editing xml files that are runtime assembled from upto thousands of smaller xml files organized in 5 level deep directory structures so there locating and editing a file is easier with synctex clicks) 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 -----------------------------------------------------------------