From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from cgl.ntg.nl (Cgl.ntg.nl [5.39.185.202]) by inbox.vuxu.org (Postfix) with ESMTP id 5B14E24248 for ; Sat, 13 Apr 2024 19:53:16 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by cgl.ntg.nl (Postfix) with ESMTP id 9EA964841C9 for ; Sat, 13 Apr 2024 19:52:01 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at cgl.ntg.nl Authentication-Results: cgl.ntg.nl (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=jdvb.ca Received: from cgl.ntg.nl ([127.0.0.1]) by localhost (cgl.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YL6s0B7_9AXy for ; Sat, 13 Apr 2024 19:52:01 +0200 (CEST) Received: from cgl.ntg.nl (localhost [127.0.0.1]) by cgl.ntg.nl (Postfix) with ESMTP id 41B774841DA for ; Sat, 13 Apr 2024 19:51:19 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by cgl.ntg.nl (Postfix) with ESMTP id 324BC483E06 for ; Sat, 13 Apr 2024 19:50:49 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at cgl.ntg.nl Received: from cgl.ntg.nl ([127.0.0.1]) by localhost (cgl.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4LMB-vTM-aka for ; Sat, 13 Apr 2024 19:50:48 +0200 (CEST) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=67.215.8.18; helo=se2.web-dns1.com; envelope-from=zlists+context@jdvb.ca; receiver= Received: from se2.web-dns1.com (se2.web-dns1.com [67.215.8.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by cgl.ntg.nl (Postfix) with ESMTPS id C0EF7483E01 for ; Sat, 13 Apr 2024 19:50:48 +0200 (CEST) Received: from mailpro1.whc.ca ([51.79.16.13]) by se1.web-dns1.com with esmtps (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rvhWX-00E4QZ-EJ for ntg-context@ntg.nl; Sat, 13 Apr 2024 13:50:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=jdvb.ca; s=default; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:To:From:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=OkL4e+DgD3eGc21DFO1qX4wiQGN9msYdmxkWHF5xxrs=; b=cm/v3RB493FspjvoKEnwjY6pid KwIhh6GYPDifhdAlkIoxUb1/qJDC6aszQMJ3yTuy59IU4+aDsvvQFFjiyTwyMblvRo3fIwd/3zRho bwoX5BqmgO9jVsdADFEQXOz52uRjdb+z6kdAgrvuKqdo95avINipzzFYJElXFwrC/poGrlIuoY1KF lBVI8RLB6/Sr5y7NgTAphLCLeg6auy8YDsfuReD8AS3ONrNcTWmdiboUxCQvXx1fhUhiQzXBJBFkS 0E5yII7S8enJg316gXWrPoi2yd0DvccenLSUgB643BJvjJMfEcdsgGTMKo/BYqWaQDkWdynNriMOg BsnkhATA==; Received: from [47.55.144.2] (port=59724 helo=x360) by mailpro1.whc.ca with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1rvhWP-002dT2-0l for ntg-context@ntg.nl; Sat, 13 Apr 2024 13:50:43 -0400 Received: by x360 (Postfix, from userid 1000) id C5CFD1E07FB; Sat, 13 Apr 2024 14:50:36 -0300 (ADT) Date: Sat, 13 Apr 2024 14:50:36 -0300 From: Jim To: mailing list for ConTeXt users Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Microslop: Just say no X-Originating-IP: 51.79.16.13 X-SpamExperts-Domain: out.mailpro1.whc.ca X-SpamExperts-Username: 51.79.16.13 Authentication-Results: web-dns1.com; auth=pass smtp.auth=51.79.16.13@out.mailpro1.whc.ca X-SpamExperts-Outgoing-Class: unsure X-SpamExperts-Outgoing-Evidence: Combined (0.32) X-Recommended-Action: accept X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT/+KfaHcMMLm15IXStjmjVPPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5x+OkQ6e4TPVgvpcS1fNw4ZIpdOJ9Sgfu6rKL8kf6cp2WkE r6CODzkd0dTEJMu1/GfilbHtbFYVmmyNP/jzd7CCzPgfBgZM0FjuQW6Y55dUiQZmnW/XN+tohdLu D74c7RJNKxFs2c4lcs0C+6HrbOWFg8CBO1Snvm6qXHQp7O9kdfVx4GsWPrj5Abbqhk9i9oABGzKf EMfQP5IsMlZ0RJfO3ceUEtcBrRN3cOZEdcQPT+ZG1fUd+zsVv0CjT0c5StJuxHTyr20QCMWbZvJ/ 43O0YO/Ae1h1hLGGi4ebv387haIyTxfBkXia0fODtmvCePe9o1PoItNcDLylAM0FmDr5gO1wm8NE k1wbhGTfLxHk2mErPLbt0n54j3vHX4q9ucblgTl6fJxyntEfhZCKje4ZIikIfn4yKSMV12lQWi2L RJlKOaZVvWPNYKOkeGHVaNmpda9O3Jm3n4TasdFPGI49Ap/fepC1NisM+LESvgPZp60jiD6XqsJZ tjQxlyCdsewEIxd5o9D/0kLc7qzMpBxbZ+JCsx9Jyu6yy20BRzxfApVJM+T/l+jhOSdSX6s3GZ29 TSUP9pNNO4SMeO0FFB1gyOR8MUyig2lXdY8S0Bvx6bc4WO8ylm36CLwDWmeZYasaPP1kYPMixNx2 mes6KVOe+i6awP4TrmTo/B6iNUbugUj67laESn7sQvNyrNVxqRBkDD9jQ1dvL800KrFfgF5eHHAS JNUmoOHSoqgqxfHmWZc1VI0OUEuQUoHVL1MiJ5eVHaOwIjyu0ei8ys9bVixM8EXMjS0ORlX4sz17 SRzsXl84a8BpwztrWhkjyht5W1g0gnAj3OTWbg9oZ+/t7CVSnVawqTUtEkl9reoB2cpvNTTmDyM+ MpzGu6WUOIYvxxqbaL3L+dEKbTHisHJTB/aFxaaCg+P6sn7OKqOpDgBvfw== X-Report-Abuse-To: spam@se1.web-dns1.com Message-ID-Hash: GU4VNLEGCBHHLC32LSZELODCLXLUITA6 X-Message-ID-Hash: GU4VNLEGCBHHLC32LSZELODCLXLUITA6 X-MailFrom: zlists+context@jdvb.ca X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.8 Precedence: list Reply-To: mailing list for ConTeXt users Subject: [NTG-context] Re: Most recent context doesn't like synctex? List-Id: mailing list for ConTeXt users Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Thanks for the quick reply. On Sat, Apr 13, 2024 at 09:18 (+0200), Hans Hagen wrote: > 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 I guess one person's bug is another person's 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 Are these recent changes? And should emacs+auctex+PDFview work now? > - we assume that synctex is set up in the document with > \setupsynctex[state=start] > \setupsynctex[state=repeat] % less efficient but gets around issue I haven't been using either of those, since auctex does The Right Thing for me. Or, at least, it used to. > - 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 I (think I) see what you are saying, but if one explicitly uses --synctex on the command line, should that not over-ride the over-ride? Or, put another way, would the following not make sense: if --synctex is used on the command line create synctex file else if --nonstop is used on the command line do not create the synctex file else if \setupsynctex[...] is used in the source file create the synctex file else do not create the synctex file > - the manual has been updates Ummm... I hunted around for a while, but I did not find out which manual was updated. The synctex wiki page has not been updated, nor has the "workflow support in context" manual. Can you tell me which manual I should go look at? > - running context in nonstop mode makes little sense Guessing wildly, I assume the auctex author(s) didn't want processes sitting there waiting for input on errors, like plain TeX would normally do. But perhaps the addition of --nonstopmode for ConTeXt is incorrect and/or redundant in April of 2024. > (maybe, as power user, Mikael remembers more details) Mikael? Any thoughts to share? Cheers. 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 ___________________________________________________________________________________