From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: "Cezary Drożak" <czarek@drozak.net>,
"mailing list for ConTeXt users" <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: SyncTeX does not work with Zathura
Date: Sun, 10 Oct 2021 22:54:04 +0200 [thread overview]
Message-ID: <74d5af80-ab94-7555-b440-0118eea66460@xs4all.nl> (raw)
In-Reply-To: <1633886093282.939557578.1530300174@drozak.net>
On 10/10/2021 7:20 PM, Cezary Drożak wrote:
> > you can play with
> >
> > mtxrun --script synctex
> >
> > and the synctex file to see if it makes sense
> I wrote two almost identical files in plain tex and context. When I
> generated the synctex file and ran `mtxrun --script synctex --list
> x.synctex` I got this:
>
> ```
> $ mtxrun --script synctex --list context.synctex
> mtx-synctex | begin page: 1
> mtx-synctex | end page: 1
>
> $ mtxrun --script synctex --list tex.synctex
> mtx-synctex | begin page: 1
> mtx-synctex | [ 72 82 92 82] : 1 :
> /home/nawordar/tests/tex/hello/./tex.tex
> mtx-synctex | end page: 1
> ```
>
> It looks like context generates an incomplete synctext file.
I can't say ... what is missing? Can you figure out what makes Zathura
unhappy?
The context synctex files are definitely less verbose because (1) we
avoid clutter, (2) omit auto-generated content like pagenumbers and so,
(3) collapse ranges (which we can do because we know what we're dealing
with), (4) don't compress (because it makes no sense), (5) ignore
styles, (6) also handle xml, etc. There have been some changes between
synctex 1 and 2 but I don['t keep track of that. Actually, if a 'call
some command' approach would have been chosen we could have better
readable files (in our case lua or so).
> > one problem with synctex is that the editors depend on a library and
> there has been changes
> >
> > texshop now uses the more independent method for context i.e. just
> calling "mtxrun --script synctex ..." which not only removes the
> dependency of a library (the dependency on mtxrun is ok as one has
> context anyway) but also permits room for improvement (apart from not
> being tricked by latex specific heuristics in the library)
>
> But that would need a change in Zathura wouldn't it?
sure, so unlikely to happen soon (i have no influence on that)
(but it would have been a better approach anyway, not being dependent on
libraries that that depend on specific synctex versions in tex as well
as heuristics; basically now one needs a version of the editor/viewer
that matches a tex engine); one doesn't hard code a pdf viewer in an
editor either (btw, the script approach permits two way sync, so in
texshop one can go from pdf to source and source to pdf)
here with
\starttext
Hello, world!
\stoptext
i get
SyncTeX Version:1
Input:1:oeps.tex
Output:pdf
Magnification:1000
Unit:1
X Offset:0
Y Offset:0
Content:
!103
{1
[0,0:0,0:0,0,0
v0,0:0,55380990:39158276,55380990,0
h1,6:4661756,9176901:4275840,655360,327680
]
!104
}1
!8
Postamble:
Count:3
!22
Post scriptum:
(also with context --synctex oeps)
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-10-10 20:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <546d4350-5561-57a3-c963-584fc65e1a9c@drozak.net>
2021-10-10 16:11 ` Cezary Drożak via ntg-context
2021-10-10 16:59 ` Hans Hagen via ntg-context
2021-10-10 17:20 ` Cezary Drożak via ntg-context
2021-10-10 20:54 ` Hans Hagen via ntg-context [this message]
2021-10-11 10:32 ` Cezary Drożak via ntg-context
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=74d5af80-ab94-7555-b440-0118eea66460@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=czarek@drozak.net \
--cc=j.hagen@xs4all.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).