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
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 -----------------------------------------------------------------
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
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 -----------------------------------------------------------------
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
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 -----------------------------------------------------------------
participants (5)
-
Hans Hagen -
Hartmut Henkel -
Mojca Miklavec -
Vyatcheslav Yatskovsky -
Wolfgang Schuster