LaTeX-Workshop: Ensure any running recipe stops before starting a new compilation

Is your feature request related to a problem? Please describe. Using arara for my recipe, when the recipe returns an error, I often get a large amount of non terminated compilation process if I do not pay attention to kill every one of them manually

Describe the solution you’d like I would be nice that starting a new recipe automatically kills all previous hanging recipes and related tasks to avoid crowding the system with hidden useless tasks.

Describe alternatives you’ve considered Extend the capability of the kill-process switcth to former recipes

Additional context

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 33 (4 by maintainers)

Most upvoted comments

Hello, Paulo here!

First of all, thank you very much for this amazing extension to VS Code! It’s been a while since I used the editor in my Linux box (I usually stick with my vim setup), but I am sure I used the LaTeX Workshop extension at a certain point before. So kudos to everybody involved in the project!

I am part of the team behind arara, so it’s interesting to see our project paths crossing, although it is a bit uncomfortable as we have an issue to tackle. However, I always take a positive approach at these situations as a great opportunity to improve code and also to gather with fellow developers who devote their time in these open source endeavours. 😉

Since there’s an ongoing discussion, I will refrain from now, as I tend to talk too much. 😉 This is just a friendly poke at the developers to keep up their good work and also offer our (the arara team) help and attention in order to provide the best user experience regarding TeX and friends.

Cheerio!

cereda on Mar 24, 2020

Speaking from the arara perspective: We develop arara as a transparent layer that only pipes input/output. Hence, we do not see it as our task to do what you ask for.

They say that arara v5 is not supposed to be used with LaTeX Workshop and other IDEs. We can do nothing on our side.

We did not say that and we do not want to suggest anybody not to use an IDE to work with arara. But maybe VS Code (which I do not know) is unable to achieve what other editors/IDEs (TeXworks, vim and emacs are the ones I know) get right. The formerly named editors provide a transparent input/output window for user interaction and their kill does work like it does on the command-line.

No. It means that arara behaves differently when executed from the command line. It depends on how to handle signals. Report to https://github.com/cereda/arara.

I noticed how subprocess kills are handled in Linux:

https://github.com/James-Yu/LaTeX-Workshop/blob/933f095c1f1cb9ceeaeae6d98f077dad2b902f4e/src/components/builder.ts#L51-L53

That is, you kill all subprocesses manually. But only on Linux. Maybe for the sake of consistency it would be worth to also enable a similar piece of code on Windows. That would solve this issue.

TheTeXnician on Mar 24, 2020