ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: 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 18:59:00 +0200	[thread overview]
Message-ID: <76af5891-7c11-3185-bccb-f14cefcbf3ee@xs4all.nl> (raw)
In-Reply-To: <6b4b4dba-486d-b76d-8571-70da07942856@drozak.net>

On 10/10/2021 6:11 PM, Cezary Drożak via ntg-context wrote:
> Hello,
> I have been trying to get SyncTeX to work with ConTeXt and Zathura, but 
> nothing
> seems to work.
> 
> I created a simple `hello.mklx` file and ran `context --synctex=-1 
> hello.mklx`.
> Then I launched Zathura with `zathura -x "nvr -cc \"call 
> vimtex#view#reverse_goto(%{line}, '%{input}')\" --nostart" hello.pdf`.
> When I clicked "Hello, world!" while holding a control key it printed the
> following error to console:
> 
> ```
> (org.pwmt.zathura:80241): GLib-CRITICAL **: 15:49:12.359: 
> g_variant_new_string: assertion 'string != NULL' failed
> warning: Failed to obtain data via SyncTeX or data is incomplete.
> ```
> 
> I am attaching the `hello.mklx`, `hello.pdf` files and the generated 
> `hello.synctex` file. I am getting the same result with `--synctex=1`.
you can play with

mtxrun --script synctex

and the synctex file to see if it makes sense

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)

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:[~2021-10-10 16:59 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 [this message]
2021-10-10 17:20     ` Cezary Drożak via ntg-context
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=76af5891-7c11-3185-bccb-f14cefcbf3ee@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --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).