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
First of all: Great work @James-Yu and @Arxisos in fully integrating my idea of #302 into this extension. This works great on every plattform.
Like another user also mentioned in #302 (comment), some may want to use a specific docker image including e.g. additional tools or a newer texlive version. Of course some could just re-tag a downloaded Docker image to tianon/latex to use it via Latex-Workshop, use the "manual way" I described in #302 or use @Arxisos shims (https://github.com/Arxisos/LaTex-Workshop-Docker) - but an option in the settings for configuring this maybe would be even more user friendly.
For the implementation I think the easiest way would be to set an environment variable before executing the scripts for *nix/Windows and using this environment variable in these scripts.
The text was updated successfully, but these errors were encountered:
It seems possible with ${@:2} replacing $@ and $1 as the docker image in the scripts. However I currently do not have access to computers with docker. It may rely on the community effort.
First of all: Great work @James-Yu and @Arxisos in fully integrating my idea of #302 into this extension. This works great on every plattform.
Like another user also mentioned in #302 (comment), some may want to use a specific docker image including e.g. additional tools or a newer texlive version. Of course some could just re-tag a downloaded Docker image to
tianon/latex
to use it via Latex-Workshop, use the "manual way" I described in #302 or use @Arxisos shims (https://github.com/Arxisos/LaTex-Workshop-Docker) - but an option in the settings for configuring this maybe would be even more user friendly.For the implementation I think the easiest way would be to set an environment variable before executing the scripts for *nix/Windows and using this environment variable in these scripts.
The text was updated successfully, but these errors were encountered: