ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Nicola <nvitacolonna@gmail.com>
Subject: Re: Synctex broken in LMTX ?
Date: Thu, 20 May 2021 23:24:18 +0200	[thread overview]
Message-ID: <edae1026-f44b-d699-7630-70323ce4eec1@xs4all.nl> (raw)
In-Reply-To: <s86ds3$3ib$1@ciao.gmane.io>

On 5/20/2021 9:38 PM, Nicola wrote:
> On 2021-05-16, Hans Hagen <j.hagen@xs4all.nl> wrote:
>> On 5/16/2021 5:30 PM, Nicola wrote:
>>
>>> Anyway, I am positive that he is willing to support ConTeXt in the best
>>> possible way...
>>
>> Sure. I met him a few times. Definitely an asset for the tex community.
>>
>>>> see? the info is just there, so you can try to convince the texshop
>>>> creator to support this:
>>>>
>>>>      -- call an external program with these arrguments (the texhop editor
>>>> knows the positions as it has the viewer built in)
>>>>      -- go to reported file and line
>>>
>>> ...which could be as well this.
>> Feel free to ask him,
> 
> I've got a positive feedback, and the summer as an estimated time to
> start working on it. One thing he asked is what I was asking you: it
> would be useful if there were a way to sync in the other direction as
> well.
You mean sort of trying to deduce from the synctex file where to go in 
the pdf? When the 'call external program' approach is used I can have an 
alternative (lua) output that is easier and might do that (less work). 
Lets first go one direction.

I only have a very old macbook and an old imac i once got so no real 
equipment to test anythign modern.

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-05-20 21:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-16 12:52 Otared Kavian
2021-05-16 14:53 ` Hans Hagen
2021-05-16 15:30   ` Nicola
2021-05-16 20:08     ` Hans Hagen
2021-05-17 13:35       ` Nicola
2021-05-20 19:38       ` Nicola
2021-05-20 21:24         ` Hans Hagen [this message]
2021-05-21  8:50           ` Nicola
2021-05-21  9:07             ` Hans Hagen
2021-05-21 10:37               ` Nicola
2021-05-16 16:57   ` Otared Kavian
2021-05-29 18:17   ` Nicola
2021-05-16 14:58 ` Hans Hagen

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=edae1026-f44b-d699-7630-70323ce4eec1@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=nvitacolonna@gmail.com \
    /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).