GNU bug report logs - #70399
ConTeXT options need updating

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 70399 in the body.
You can then email your comments to 70399 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jim <zlists+context <at> jdvb.ca>
To: bug-auctex <at> gnu.org
Subject: ConTeXT options need updating
Date: Mon, 15 Apr 2024 10:36:18 -0300

Emacs  : GNU Emacs 27.2 (build 1, x86_64-slackware-linux-gnu, GTK+ Version 3.24.27) of 2021-03-25
Package: 14.0.3.2024-03-17

Some of the ConTeXt-specific features are a bit outdated, and, as of
recently, arguably broken.

(1) TeX-command-list contains the following
    ("ConTeXt" "%(cntxcom) --once --texutil %(extraopts) %(execopts)%t"
    and --texutil isn't in texlive 2023's context, texlive 2024's context,
    or the context in the ConTeXt distribution.

(2) A recent change (early April 2024?) to context has changed how
    synctex is done.
    On the good side, with the right option context will produce a
    synctex file that epdfinfo knows how to parse.
    On the bad side,
    (a) rather than calling with "--synctex=1" (as done in
        ConTeXt-expand-options in context.el) the correct option is now
        "--synctex=repeat";
    (b) but if context is called with "--nonstopmode" (or "--nonstop")
        the "--synctex=..." request to create a synctex file is over-ridden.
    It is easy for a user who knows what is going on to use
        (setq ConTeXt-texexec-option-nonstop "")
    but changing --synctex=1 to --synctex=repeat seems to require
    a redefinition of the function.

The --synctex=repeat version may not have reached texlive 2024 yet, but
using --synctex=repeat with the version of context in TL2024 creates the
same synctex file as --synctex=1, so there seems to be no harm in
changing this.

In case it wasn't clear:
What I expected to happen:
        running context would create a synctex file.
What happened (with new context):
        the synctex file was not created.

Thanks.

                                Jim

Bonus "bug": TeX-submit-bug-report suggests upgrading to the version from
https://www.gnu.org/software/auctex, but as of today that would be a
downgrade, since it says the current auctex version is 13.3.

Message #8 received at 70399 <at> debbugs.gnu.org (full text, mbox):

From: Ikumi Keita <ikumi <at> ikumi.que.jp>
To: Jim <zlists+context <at> jdvb.ca>
Cc: 70399 <at> debbugs.gnu.org
Subject: Re: bug#70399: ConTeXT options need updating
Date: Thu, 18 Apr 2024 15:31:34 +0900

Hi Jim,

Thank you for your report. None of the AUCTeX maintainer uses ConTeXt,
so inputs from ConTeXt user are valuable.

>>>>> Jim <zlists+context <at> jdvb.ca> writes:
> (1) TeX-command-list contains the following
>     ("ConTeXt" "%(cntxcom) --once --texutil %(extraopts) %(execopts)%t"
>     and --texutil isn't in texlive 2023's context, texlive 2024's context,
>     or the context in the ConTeXt distribution.

It is easy to remove "--texutil", but I'd like to ask whether it is safe
for older (before 2023) TeX distribution to do so. What was this option
"--texutil" for? Unfortunately, "context --help" of TeX Live 2024
doesn't give me useful information.

> (2) A recent change (early April 2024?) to context has changed how
>     synctex is done.
>     On the good side, with the right option context will produce a
>     synctex file that epdfinfo knows how to parse.
>     On the bad side,
>     (a) rather than calling with "--synctex=1" (as done in
>         ConTeXt-expand-options in context.el) the correct option is now
>         "--synctex=repeat";
>     (b) but if context is called with "--nonstopmode" (or "--nonstop")
>         the "--synctex=..." request to create a synctex file is over-ridden.
>     It is easy for a user who knows what is going on to use
>         (setq ConTeXt-texexec-option-nonstop "")
>     but changing --synctex=1 to --synctex=repeat seems to require
>     a redefinition of the function.

> The --synctex=repeat version may not have reached texlive 2024 yet, but
> using --synctex=repeat with the version of context in TL2024 creates the
> same synctex file as --synctex=1, so there seems to be no harm in
> changing this.

OK, then I'll change "--synctex=1" to "--synctex=repeat", expecting that
the situation about compatibility is the same for older ConTeXt.

> Bonus "bug": TeX-submit-bug-report suggests upgrading to the version from
> https://www.gnu.org/software/auctex, but as of today that would be a
> downgrade, since it says the current auctex version is 13.3.

The message is followed by "if your installation is older than the one
available from the web site.", isn't it? 🙂

Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
#Gaza #StopMassiveKilling #CeasefireNOW

Message #11 received at 70399 <at> debbugs.gnu.org (full text, mbox):

From: Jim <zlists+context <at> jdvb.ca>
To: Ikumi Keita <ikumi <at> ikumi.que.jp>
Cc: 70399 <at> debbugs.gnu.org
Subject: Re: bug#70399: ConTeXT options need updating
Date: Thu, 18 Apr 2024 17:47:34 -0300

Hi Ikumi,

On Thu, Apr 18, 2024 at 15:31 (+0900), Ikumi Keita wrote:

> Thank you for your report.  None of the AUCTeX maintainer uses ConTeXt, so
> inputs from ConTeXt user are valuable.

Glad you think so!

>>>>>> Jim <zlists+context <at> jdvb.ca> writes:
>> (1) TeX-command-list contains the following
>>     ("ConTeXt" "%(cntxcom) --once --texutil %(extraopts) %(execopts)%t"
>> and --texutil isn't in texlive 2023's context, texlive 2024's context,
>> or the context in the ConTeXt distribution.

> It is easy to remove "--texutil", but I'd like to ask whether it is safe
> for older (before 2023) TeX distribution to do so. What was this option
> "--texutil" for? Unfortunately, "context --help" of TeX Live 2024
> doesn't give me useful information.

I am a relatively recent ConTeXt convert, so I have never used it.
However, the documentation I can find indicates that texutil was used for
ConTeXt Mk II, which has (long since) been deprecated (as I understand it).

I guess since it doesn't hurt anything, it could stay, but I think that it
has no use in ConTeXt Mk IV.

>> (2) A recent change (early April 2024?) to context has changed how
>> synctex is done.
>> On the good side, with the right option context will produce a
>> synctex file that epdfinfo knows how to parse.
>> On the bad side,
>>     (a) rather than calling with "--synctex=1" (as done in
>> ConTeXt-expand-options in context.el) the correct option is now
>>         "--synctex=repeat";
>>     (b) but if context is called with "--nonstopmode" (or "--nonstop")
>> the "--synctex=..." request to create a synctex file is over-ridden.
>> It is easy for a user who knows what is going on to use
>>         (setq ConTeXt-texexec-option-nonstop "")
>> but changing --synctex=1 to --synctex=repeat seems to require
>> a redefinition of the function.

>> The --synctex=repeat version may not have reached texlive 2024 yet, but
>> using --synctex=repeat with the version of context in TL2024 creates the
>> same synctex file as --synctex=1, so there seems to be no harm in
>> changing this.

> OK, then I'll change "--synctex=1" to "--synctex=repeat", expecting that
> the situation about compatibility is the same for older ConTeXt.

Thanks.

>> Bonus "bug": TeX-submit-bug-report suggests upgrading to the version from
>> https://www.gnu.org/software/auctex, but as of today that would be a
>> downgrade, since it says the current auctex version is 13.3.

> The message is followed by "if your installation is older than the one
> available from the web site.", isn't it? 🙂

Good point!

Cheers.
                                Jim

Message #14 received at 70399 <at> debbugs.gnu.org (full text, mbox):

From: Ikumi Keita <ikumi <at> ikumi.que.jp>
To: Jim <zlists+context <at> jdvb.ca>
Cc: 70399 <at> debbugs.gnu.org
Subject: Re: bug#70399: ConTeXT options need updating
Date: Sat, 20 Apr 2024 17:44:49 +0900

Hi Jim,

>>>>> Jim <zlists+context <at> jdvb.ca> writes:
>> It is easy to remove "--texutil", but I'd like to ask whether it is safe
>> for older (before 2023) TeX distribution to do so. What was this option
>> "--texutil" for? Unfortunately, "context --help" of TeX Live 2024
>> doesn't give me useful information.

> I am a relatively recent ConTeXt convert, so I have never used it.
> However, the documentation I can find indicates that texutil was used for
> ConTeXt Mk II, which has (long since) been deprecated (as I understand it).

> I guess since it doesn't hurt anything, it could stay, but I think that it
> has no use in ConTeXt Mk IV.

I see, thanks. I guess this option is necessary for only rather old
context binaries and expect it can be removed safely for now.

>>> (b) but if context is called with "--nonstopmode" (or "--nonstop")
>>> the "--synctex=..." request to create a synctex file is over-ridden.
>>> It is easy for a user who knows what is going on to use
>>> (setq ConTeXt-texexec-option-nonstop "")

Do you think AUCTeX should do smart action to avoid "--nonstopmode" when
"--synctex" is requested by the user, so that
(setq ConTeXt-texexec-option-nonstop "")
isn't necessary on the user side? It isn't difficult to have
"--nonstopmode" only when `TeX-source-correlate-mode' and
`TeX-interactive-mode' are nil.

Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
#Gaza #StopMassiveKilling #CeasefireNOW

Message #17 received at 70399 <at> debbugs.gnu.org (full text, mbox):

From: Jim <zlists+context <at> jdvb.ca>
To: Ikumi Keita <ikumi <at> ikumi.que.jp>
Cc: 70399 <at> debbugs.gnu.org
Subject: Re: bug#70399: ConTeXT options need updating
Date: Sat, 20 Apr 2024 12:37:08 -0300

Hi Ikuma,

On Sat, Apr 20, 2024 at 17:44 (+0900), Ikumi Keita wrote:

> Hi Jim,

>>>>>> Jim <zlists+context <at> jdvb.ca> writes:
>>> It is easy to remove "--texutil", but I'd like to ask whether it is safe
>>> for older (before 2023) TeX distribution to do so. What was this option
>>> "--texutil" for? Unfortunately, "context --help" of TeX Live 2024
>>> doesn't give me useful information.

>> I am a relatively recent ConTeXt convert, so I have never used it.
>> However, the documentation I can find indicates that texutil was used for
>> ConTeXt Mk II, which has (long since) been deprecated (as I understand it).

>> I guess since it doesn't hurt anything, it could stay, but I think that it
>> has no use in ConTeXt Mk IV.

> I see, thanks. I guess this option is necessary for only rather old
> context binaries and expect it can be removed safely for now.

I expect so as well.  ConTeXt is a bit of a moving target, and (like many
other software tools) if someone is having any issues with it, I feel
confident in saying the developers and the rest of the community will tell
people to upgrade to the latest and greatest before any help can be
provided.

>>>> (b) but if context is called with "--nonstopmode" (or "--nonstop")
>>>> the "--synctex=..." request to create a synctex file is over-ridden.
>>>> It is easy for a user who knows what is going on to use
>>>> (setq ConTeXt-texexec-option-nonstop "")

> Do you think AUCTeX should do smart action to avoid "--nonstopmode" when
> "--synctex" is requested by the user, so that
> (setq ConTeXt-texexec-option-nonstop "")
> isn't necessary on the user side?  It isn't difficult to have
> "--nonstopmode" only when `TeX-source-correlate-mode' and
> `TeX-interactive-mode' are nil.

I think that would be an even nicer solution!  I will point out that the
Head Honcho of ConTeXT said (on the ConTeXT users mailing list)
        - running context in nonstop mode makes little sense

He did not elaborate on that comment.  However, I note that when context
finds an error in an input file, even without -nonstopmode, the process
terminates (in a few tests I did) , unlike (e.g.,) pdftex, which as you
know waits for user input.

I spent a few minutes trying various command line options and commands
inside the source file, and I can't get context to stop on error and wait
for input.  This doesn't mean that there is no way to do it, and poking
through the code I see a lot of code related to 'nonstopmode' and
'errorstopmode', but I don't know how to make context stop on an error and
wait for input.

I could ask for clarification about this on the context users' list if you
would like to hear a more authoritative opinion before making changes.  Let
me know.

Cheers.

                                Jim

Message #20 received at 70399 <at> debbugs.gnu.org (full text, mbox):

From: Ikumi Keita <ikumi <at> ikumi.que.jp>
To: Jim <zlists+context <at> jdvb.ca>
Cc: 70399 <at> debbugs.gnu.org
Subject: Re: bug#70399: ConTeXT options need updating
Date: Sun, 21 Apr 2024 16:38:50 +0900

Hi Jim,

>>>>> Jim <zlists+context <at> jdvb.ca> writes:
>> Do you think AUCTeX should do smart action to avoid "--nonstopmode" when
>> "--synctex" is requested by the user, so that
>> (setq ConTeXt-texexec-option-nonstop "")
>> isn't necessary on the user side?  It isn't difficult to have
>> "--nonstopmode" only when `TeX-source-correlate-mode' and
>> `TeX-interactive-mode' are nil.

> I think that would be an even nicer solution!  I will point out that the
> Head Honcho of ConTeXT said (on the ConTeXT users mailing list)
>         - running context in nonstop mode makes little sense

> He did not elaborate on that comment.  However, I note that when context
> finds an error in an input file, even without -nonstopmode, the process
> terminates (in a few tests I did) , unlike (e.g.,) pdftex, which as you
> know waits for user input.

> I spent a few minutes trying various command line options and commands
> inside the source file, and I can't get context to stop on error and wait
> for input.  This doesn't mean that there is no way to do it, and poking
> through the code I see a lot of code related to 'nonstopmode' and
> 'errorstopmode', but I don't know how to make context stop on an error and
> wait for input.

Thanks, I pushed the fix including the change to omit --nonstop option
when --synctex option is present.

> I could ask for clarification about this on the context users' list if you
> would like to hear a more authoritative opinion before making changes.  Let
> me know.

Thanks, I don't think that's necessary. I'll close this bug.

Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
#Gaza #StopMassiveKilling #CeasefireNOW

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.