Proposal - make synctex command configurable

Will it be possible to make synctex command configurable from the settings file?

I am trying to run all LaTeX commands within docker containers. I am able to run both toolchain and chktex commands, for example, with these settings:

"latex-workshop.linter_command_active_file": [
  "sh",
  "-c",
  "docker run --rm -i -v $(pwd):$(pwd) -w $(pwd) harmish/latex chktex -wall -n22 -n30 -e16 -q -I0 -f%f:%l:%c:%d:%k:%n:%m\n"
],
"latex-workshop.linter_command_root_file": [
  "sh",
  "-c",
  "docker run --rm -i -v $(pwd):$(pwd) -w $(pwd) harmish/latex chktex -wall -n22 -n30 -e16 -q -f%f:%l:%c:%d:%k:%n:%m %DOC%.tex\n"
],
"latex-workshop.toolchain": [
  "docker run --rm -t -v $(pwd):$(pwd) -w $(pwd) harmish/latex latexmk -synctex=1 -interaction=nonstopmode -file-line-error -pdf %DOC%.tex"

Same way, it would be great if I can invoke the synctex command also from within a container.

I quickly checked by replacing synctex with docker run --rm -i -v $(pwd):$(pwd) -w $(pwd) harmish/latex synctex in lines 66 and 78, which works fine.

And thank you, the authors, for creating this nice and powerful extension.

[James-Yu]

Great! Will work on that.

What I suppose is that the API should support reading configs even not registered in package.json. If so, we can pop red alerts when the global/workspace config has obsolete config keys and encourage users to adopt the new pattern. I’ll have a short AFK and return with some more things!

[harmishhk]

@jabooth thank you for the information. The new way of defining configurations seems better. However, my docker related configurations had problems with this solution. It is combination of how spawn of child_process works and how configuration strings are passed on to docker. But, I have found a better way of defining LaTeX commands with docker. Rather then playing with configurations, I just added a small executable script latexmk in my PATH, for Linux it would be like:

#!/bin/bash
docker run --rm -i -v $(pwd):$(pwd) -w $(pwd) harmish/latex latexmk "$@"

With this I do not need to change configuration in LaTeX-Workshop at all, and this should work regardless of using spawn or exec and whatever tool I’m using to call latexmk. Similar script for chktex also works fine 😃.