ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: synctex
Date: Sun, 4 Jun 2017 18:55:55 +0200	[thread overview]
Message-ID: <4a7b796b-2273-1d0c-3f9d-b815977226ea@wxs.nl> (raw)

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
___________________________________________________________________________________

             reply	other threads:[~2017-06-04 16:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-04 16:55 Hans Hagen [this message]
2017-07-11 14:36 ` synctex Thomas Floeren
2017-07-11 15:09   ` synctex Hans Hagen
2017-07-11 21:06     ` synctex Thomas Floeren
2017-07-19  9:05       ` synctex Thomas Floeren
  -- strict thread matches above, loose matches on Subject: below --
2014-06-03  9:44 SyncTeX Trond Thorbjørnsen
2014-06-03 10:03 ` SyncTeX Mojca Miklavec
2014-06-03 14:09   ` SyncTeX Trond Thorbjørnsen
     [not found] <mailman.1.1252749604.19174.ntg-context@ntg.nl>
2009-09-12 11:08 ` synctex Vyatcheslav Yatskovsky
2009-09-12 11:22   ` synctex Hans Hagen
2009-09-12 14:55     ` synctex Wolfgang Schuster
2009-09-13 10:45       ` synctex Hans Hagen
2009-09-13  0:18     ` synctex Hartmut Henkel
2009-09-13  7:14       ` synctex Mojca Miklavec
2009-09-13 11:01       ` synctex Hans Hagen
2008-08-22  9:25 synctex Patrick Gundlach

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4a7b796b-2273-1d0c-3f9d-b815977226ea@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).