ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Cezary Drożak via ntg-context" <ntg-context@ntg.nl>
To: Hans Hagen <j.hagen@xs4all.nl>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Cezary Drożak" <czarek@drozak.net>
Subject: Re: SyncTeX does not work with Zathura
Date: Sun, 10 Oct 2021 17:20:56 +0000	[thread overview]
Message-ID: <1633886093282.939557578.1530300174@drozak.net> (raw)
In-Reply-To: <76af5891-7c11-3185-bccb-f14cefcbf3ee@xs4all.nl>

 > 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.

 > 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?
___________________________________________________________________________________
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:[~2021-10-10 17:20 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 [this message]
2021-10-10 20:54       ` Hans Hagen via ntg-context
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=1633886093282.939557578.1530300174@drozak.net \
    --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).