ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Thomas Floeren <thfl@mac.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: synctex
Date: Wed, 19 Jul 2017 11:05:19 +0200	[thread overview]
Message-ID: <1DA6CA83-B74D-4751-B726-FAD6F9817788@mac.com> (raw)
In-Reply-To: <E8F85B53-3131-4C33-B27F-6C1221AEF4BC@mac.com>


[-- Attachment #1.1: Type: text/plain, Size: 4113 bytes --]


> On 11. Jul 2017, at 23:06, Thomas Floeren <thfl@mac.com> wrote:
> 
>> 
>> On 11. Jul 2017, at 17:09, Hans Hagen <pragma@wxs.nl <mailto:pragma@wxs.nl>> wrote:
>> 
>> On 7/11/2017 4:36 PM, Thomas Floeren wrote:
>>>> On 4. Jun 2017, at 18:55, Hans Hagen <pragma@wxs.nl <mailto:pragma@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.)

With 2017.07.17 00:20 the issue seems to persist.

Tom


> 
> 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 <mailto:ntg-context@ntg.nl> / http://www.ntg.nl/mailman/listinfo/ntg-context <http://www.ntg.nl/mailman/listinfo/ntg-context>
> webpage  : http://www.pragma-ade.nl <http://www.pragma-ade.nl/> / http://context.aanhet.net <http://context.aanhet.net/>
> archive  : https://bitbucket.org/phg/context-mirror/commits/ <https://bitbucket.org/phg/context-mirror/commits/>
> wiki     : http://contextgarden.net <http://contextgarden.net/>
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 19348 bytes --]

[-- Attachment #2: Type: text/plain, Size: 492 bytes --]

___________________________________________________________________________________
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-07-19  9:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-04 16:55 synctex Hans Hagen
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       ` Thomas Floeren [this message]
  -- 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=1DA6CA83-B74D-4751-B726-FAD6F9817788@mac.com \
    --to=thfl@mac.com \
    --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).