From: Hans Hagen <pragma@wxs.nl>
To: news3@nililand.de, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: synctex and TeXShop problem
Date: Tue, 21 Nov 2017 16:43:53 +0100 [thread overview]
Message-ID: <da135353-040f-d106-1f51-dd4fb9213c61@wxs.nl> (raw)
In-Reply-To: <26znv9fxax7h$.dlg@nililand.de>
On 11/21/2017 2:21 PM, Ulrike Fischer wrote:
> Am Tue, 21 Nov 2017 14:15:02 +0100 schrieb Hans Hagen:
>
>
>>> synctex fails with lualatex on windows too. And it fails with with
>>> the luatex version 1.06 (which is now in miktex) but not with 1.04
>>> (texlive).
>>>
>>> I compared the synctex files of both and the problem is that the
>>> link to the main tex file is missing at the start.
>>>
>>> The synctex files refers to a lot positions in input 0 but the file
>>> list starts with
>>>
>>> Input:1:D:/MiKTeX2.9/tex/latex/base/article.cls
>>>
>>>
>>> I added before this line
>>>
>>> Input:0:G:/Z-Test/./test-utf8.tex
>>>
>>> and then synchronization worked again. Imho this is a luatex bug.
>>>
>>> (the texlive synctex starts with number 1 and not 0
>>> Input:1:G:/Z-Test/./test-utf8.tex)
>
>> i noticed this 0 /1 iusue too but it was ok in old viewers so mayeb that
>> changed .. fwiw, nothing changed in luatex where we just take the syntex
>> code as-is ... actually in sumatra starting at 1 is the only thing that
>> works
>
> I don't think that the 0/1 issue is a problem in itself -- but I
> think that the change of the numbering system introduced the real
> bug: That the line
>
> Input:0:G:/Z-Test/./test-utf8.tex
>
> is missing in the synctex file.
ok, we have a fix for that (but it doesn't explain why context generated
files make texshop unhappy)
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2017-11-21 15:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 13:19 Alan Bowen
2017-11-17 13:27 ` Otared Kavian
2017-11-17 13:31 ` luigi scarso
2017-11-17 13:50 ` Alan Bowen
2017-11-17 14:13 ` Hans Hagen
2017-11-21 12:18 ` Ulrike Fischer
2017-11-21 13:15 ` Hans Hagen
2017-11-21 13:21 ` Ulrike Fischer
2017-11-21 15:43 ` Hans Hagen [this message]
2017-11-22 8:25 ` Ulrike Fischer
2017-11-22 8:30 ` luigi scarso
2017-11-22 8:39 ` Ulrike Fischer
2017-11-22 9:27 ` luigi scarso
2017-11-22 9:34 ` Hans Hagen
2017-11-22 9:48 ` Ulrike Fischer
2017-11-22 9:57 ` Hans Hagen
2017-11-17 20:59 ` Otared Kavian
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=da135353-040f-d106-1f51-dd4fb9213c61@wxs.nl \
--to=pragma@wxs.nl \
--cc=news3@nililand.de \
--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).