CMD-click with ConTeXt component files

[texworks]

CMD-click with ConTeXt component files

[GoogleCodeExporter]

For cmd-click (synctex-based source<->preview jump) to work, you need to pass 
the -synctex=1 option on 
the pdftex or xetex command line. I haven't looked into how this should be done 
with ConTeXt; maybe you can 
pass command-line options through texmfstart?

An alternative would be to add \synctex=1 to the beginning of your source file. 
But it would be good to add this 
to the default configuration of the ConTeXt tools, if someone could confirm how 
to do it.

Original comment by [email protected] on 15 Jul 2008 at 9:24

[GoogleCodeExporter]

right, synctex needs to be activated ... i forgot that TeXShop is unique using a
sync-mechanism that doesn't require additional code to be added. wouldn't it be 
great
to have this mechanism (pdfkit?) also as an option work TeXworks?! it works so 
great
and doesn't take time nor mem!

Original comment by [email protected] on 16 Jul 2008 at 10:28

[GoogleCodeExporter]

Well, if the ConTeXt tool can be set up to pass -synctex=1 on the command line, 
then nothing has to be done 
in the actual document; I just don't know how to pass options to the TeX engine 
via ConTeXt, but I'm sure we 
can get that done somehow.

TeXShop's sync mechanism based on PDF search is great when it works, but may 
not be so reliable on large or 
complex documents. It sometimes struggles with complex fonts, too, that can 
confuse the PDF search feature.

It might be nice to do a similar thing in TeXworks some day, but it can't be 
based on PDFkit as that's an 
Apple-specific framework. For portability, we'd have to use Poppler's text 
extraction facilities as the basis, 
and I haven't worked on this yet. But anyhow, I think that if SyncTeX is set up 
to be enabled by default in the 
tools, that will provide robust sync behavior and you won't really miss the 
other approach.

Original comment by [email protected] on 16 Jul 2008 at 10:38

[GoogleCodeExporter]

To 1: Hans promised he will implement this when TeXworks is stable.
To 2: I regularly use it on large (500 to 600 A4 pages) and not too complex
(thousands of footnotes and index marks but only latin font) documents and 
never had
any problem – lucky me ;o)
To 3: Is was just a bit in doubt cause typesetting my project takes quite long 
anyway
(for HZ's sake!) ... and Hans mentioned that synctex will use quite some time 
and
memory when typesetting. pdfkit's sync doesn't.

Original comment by [email protected] on 16 Jul 2008 at 11:53

[GoogleCodeExporter]

I'm marking this as a possible enhancement, but will not be working on it for 
the time being; ensuring synctex 
works well is a higher priority at the moment.

Original comment by [email protected] on 29 Jul 2008 at 10:09

• Changed state: Accepted
• Added labels: Type-Enhancement, Priority-Low
• Removed labels: Type-Defect, Priority-Medium

[GoogleCodeExporter]

I invoke ConTeXt like
texexec --passon="-synctex=1" $filename
and synctex works.

Original comment by [email protected] on 12 Jun 2009 at 2:09

[GoogleCodeExporter]

The latest beta (the feature that will probably end up in TL 2009) also has
    texexec --synctex filename
syntax enabled (but at the moment passon might be safer from the perspective of 
being more backward-
compatible).

Original comment by [email protected] on 15 Jun 2009 at 11:11

[stloeffler]

--synctex is passed to context since 014c504.