You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because the task execution engine built into VS Code lacks in many regards, it would be nice if a ubiquitous build system (generator) would be supported. I would argue, that CMake is perhaps the best choice. I do teach junior physicist (who have to deal with quite a lot of LaTeX in their professional life) how to automate building a library, an exe consuming it, invoking the exe for a data file, plotting the data using GnuPlot and compiling a LaTeX document using the plot in an end-to-end manner with proper dependencies being tracked by the generated build system (Ninja per say).
It would be nice if following in the footsteps of cpptools, LaTeX-workshop picked up prime-time CMake support. CMake Tools is a nice extension that should provide the hooks through its API to detect custom_command invocations relevant to LaTeX-Workshop. The feature driving IDE hooks into CMake is CMake Server Mode, a long-running (build server-like) mode of CMake that constantly monitors the scripts of CMake used to generate the build system files, as well as presenting a JSON API for the resulting CMake Configuration. Every IDE extension can query this JSON for the parts relevant to them to trigger language service features, GUI hooks, SyncTex and what not.
Currently, even though I get my resulting PDF, I cannot open it, because the extension is not aware of it/was not created by it. The authors of UseLATEX and CMake Tools are both very eager to help on their part (vector-of-bool can be unresponsive at times) and I'm sure ends can be made to meet.
This enhancement is orthogonal/supplementary to the awesome in-flight proposal of using the built-in LaTeX compilation. UseLATEX can easily be configured to use any LaTeX compiler.
The text was updated successfully, but these errors were encountered:
Description
Because the task execution engine built into VS Code lacks in many regards, it would be nice if a ubiquitous build system (generator) would be supported. I would argue, that CMake is perhaps the best choice. I do teach junior physicist (who have to deal with quite a lot of LaTeX in their professional life) how to automate building a library, an exe consuming it, invoking the exe for a data file, plotting the data using GnuPlot and compiling a LaTeX document using the plot in an end-to-end manner with proper dependencies being tracked by the generated build system (Ninja per say).
It would be nice if following in the footsteps of cpptools, LaTeX-workshop picked up prime-time CMake support. CMake Tools is a nice extension that should provide the hooks through its API to detect custom_command invocations relevant to LaTeX-Workshop. The feature driving IDE hooks into CMake is CMake Server Mode, a long-running (build server-like) mode of CMake that constantly monitors the scripts of CMake used to generate the build system files, as well as presenting a JSON API for the resulting CMake Configuration. Every IDE extension can query this JSON for the parts relevant to them to trigger language service features, GUI hooks, SyncTex and what not.
Currently, even though I get my resulting PDF, I cannot open it, because the extension is not aware of it/was not created by it. The authors of UseLATEX and CMake Tools are both very eager to help on their part (vector-of-bool can be unresponsive at times) and I'm sure ends can be made to meet.
This enhancement is orthogonal/supplementary to the awesome in-flight proposal of using the built-in LaTeX compilation. UseLATEX can easily be configured to use any LaTeX compiler.
The text was updated successfully, but these errors were encountered: