ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Most recent context doesn't like synctex?
Date: Sat, 13 Apr 2024 09:18:45 +0200	[thread overview]
Message-ID: <d21e9655-0dec-4ee8-95f1-3907b1d6c44a@xs4all.nl> (raw)
In-Reply-To: <Zhm4CHaP6/vrvGdI@x360.localdomain>

On 4/13/2024 12:39 AM, Jim wrote:
> Hi,
> 
> I have both TeXlive 2024 and the stand-alone ConTeXt distribution on my
> system.
> 
> Recently, the stand-alone ConTeXt distribution seems to not create a
> synctex file any more.  Specifically,
> 
>      /usr/local/context/tex/texmf-linux-64/bin/context --once --texutil --synctex=1 --nonstop file.tex
> 
> does not create a .synctex file (and deletes it, if it is there), whereas
> the TeXlive version
> 
>      /usr/local/texlive/2024/bin/x86_64-linux/context --once --texutil --synctex=1 --nonstop nwg_newsletter_2024_04.tex
> 
> does create the .synctex file.
> 
> 
> The ConTeXt distribution version *does* create the file if --nonstop is
> *not* used.  Knowing that, I can work around this for now, although
> emacs+auctex probably won't be happy without --nonstop.
> 
> I updated the stand-alone ConTeXt a few minutes ago, so I'm up to date on
> that.
> 
> Is this a bug introduced by some recent change?
it's more a feature

- Mikael S and i spend some time with editor/viewer combinations on 
linux in order to find ways around the different synctex libs that they use

- as a result we could make most work ok

- we assume that synctex is set up in the document with

     \setupsynctex[state=start]
     \setupsynctex[state=repeat] % less efficient but gets around issue

- when context is run 'headless' (on a server) it's often done in 
batchmode because one knows that the style works and in that case 
synctex makes no sense so we disable it; this avoids the need to patch 
the style

- the manual has been updates

- running context in nonstop mode makes little sense

(maybe, as power user, Mikael remembers more details)

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 / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2024-04-13  7:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 22:39 [NTG-context] " Jim
2024-04-13  7:18 ` Hans Hagen [this message]
2024-04-13 17:50   ` [NTG-context] " Jim
2024-04-13 20:28     ` Mikael Sundqvist
2024-04-14  9:56       ` Henning Hraban Ramm
2024-04-15 14:15         ` Jim
2024-04-15 15:38         ` Mikael Sundqvist
2024-04-15 20:31           ` Henning Hraban Ramm
2024-04-15 14:08       ` Jim

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=d21e9655-0dec-4ee8-95f1-3907b1d6c44a@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --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).