From: Jim <zlists+context@jdvb.ca>
To: ntg-context@ntg.nl
Subject: [NTG-context] Most recent context doesn't like synctex?
Date: Fri, 12 Apr 2024 19:39:04 -0300 [thread overview]
Message-ID: <Zhm4CHaP6/vrvGdI@x360.localdomain> (raw)
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?
Thanks.
Jim
___________________________________________________________________________________
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
___________________________________________________________________________________
next reply other threads:[~2024-04-12 22:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 22:39 Jim [this message]
2024-04-13 7:18 ` [NTG-context] " Hans Hagen
2024-04-13 17:50 ` 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=Zhm4CHaP6/vrvGdI@x360.localdomain \
--to=zlists+context@jdvb.ca \
--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).