emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#34645: closed (Make TeX-process-check prompt optional?)


From: GNU bug Tracking System
Subject: bug#34645: closed (Make TeX-process-check prompt optional?)
Date: Wed, 13 Mar 2024 12:41:02 +0000

Your message dated Wed, 13 Mar 2024 13:40:13 +0100
with message-id <m2y1amuwya.fsf@macmutant.fritz.box>
and subject line Re: bug#34645: Make TeX-process-check prompt optional?
has caused the debbugs.gnu.org bug report #34645,
regarding Make TeX-process-check prompt optional?
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
34645: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34645
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: Make TeX-process-check prompt optional? Date: Mon, 25 Feb 2019 12:13:51 +0000
I find myself frequently being prompted by TeX-process-check while editing a document that takes a long time to process. I always want to kill the process and start a new one.

Would it be possible to add an option to disable the prompt, or is there some reason why the prompt should always be offered?

I guess that in situations like mine an even better behaviour might be to always let a run continue until it is done, but to queue up another run when some change is outstanding. That way, one does not risk the output document not updating for a long time if frequent edits are being made and no LaTeX run ever completes, because it is always being interrupted.

Finally, I noticed one typo (version 12.1.2 of AUCTeX): the docstring of TeX-process-check says "exist", and should say "exists".

For now, I just redefined TeX-process-check in my init sequence to omit the prompt.

--

--- End Message ---
--- Begin Message --- Subject: Re: bug#34645: Make TeX-process-check prompt optional? Date: Wed, 13 Mar 2024 13:40:13 +0100 User-agent: Gnus/5.13 (Gnus v5.13)
Reuben Thomas <rrt@sc3d.org> writes:

> I think it does make sense to make it file-local, as one could be
> engaged in quite different workflows and want different behaviours.

Thanks.  I pushed that change now (406eb61fc1), so I'm closing this
report.

Best, Arash


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]