Challenges Integrating TeX Live with Visual Studio Code

[Zdenek Wagner]

Hi,

I just guess because I do not use my MacBook for development. MaC OS X
is a kind of Unix thus I think that the source of the problem can be
similar as in Linux. The terminal reads the setting by running
~/.bashrc. It is more complex in Mac OS X, because several types of
terminal are available and you should set the terminal properties to
decide, which script should be run as initialization at its startup. I
configured ~/.bashrc for all terminal types. If you start a program
from a terminal, it gets settings from it. I have just looked what I
have. When the terminal is started, it executes /etc/bashrc which
calls /etc/bashrc_Apple_Terminal and then it calls ~/.bashrc
configured by me. Thus if I change my ~/.bashrc or the system
/etc/bashrc_* is mocified, it is sufficient to close the terminal and
open a new one. However, the GUI programs do not use it, they read
settins from /etc/profile and then ~/.bash_profile thus the new
setting must be available there. On Mac my /etc/profile contains:

# System-wide .profile for sh(1)

if [ -x /usr/libexec/path_helper ]; then
       eval `/usr/libexec/path_helper -s`
fi

if [ "${BASH-no}" != "no" ]; then
       [ -r /etc/bashrc ] && . /etc/bashrc
fi

#export LC_CTYPE=en_US.UTF-8
#export LC_ALL=en_US.UTF-8

This means that It will call /etc/bashrc. In Linux, I have a similar
contents in .bash_profile which calls .bashrc. The difference is that
this is called when the GUI starts so the GUI programs do not see the
changes immediately. You have to log out and in to make the changed
settings available to GUI.

I will suggest that you make a script containing just echo $PATH and
execute it from VS Code and see whether you see the path to the TeX
Live binary. If not, try logging out and in. If even this does not
help, you have to find out where the PATH is defined and how to make
it available to GUI.

Hope this helps

Zdeněk Wagner
https://www.zdenek-wagner.eu/

ne 26. 1. 2025 v 22:21 odesílatel Don Hosek <don.hosek at gmail.com> napsal:
>
> Probably your best bet would be to ask this question at https://tex.stackexchange.com  (after first checking to see what others have said). I believe that there are existing VSCode integrations for LaTeX that work with minimal effort.
>
> -dh
>
>
> On Jan 26, 2025 at 12:45:42, Ignacio Balasch Sola <ignacio at balasch.es> wrote:
>>
>> Dear TeX Live Development Team,
>>
>>
>> I hope this message finds you well. I am reaching out to share some challenges I’ve encountered while attempting to integrate TeX Live into my Visual Studio Code (VS Code) workflow.
>>
>>
>> As a developer, I prefer to use VS Code as my primary development environment across various programming languages, including LaTeX. I appreciate its versatility and the convenience of managing multiple projects within a single interface. However, integrating TeX Live with VS Code has proven to be quite challenging.
>>
>>
>> Despite dedicating considerable time and effort, I have been unable to achieve a seamless setup. I documented my process in this github discussion post https://github.com/James-Yu/LaTeX-Workshop/discussions/4518 .  The process has been fraught with difficulties, and I find myself at an impasse. I am reaching out to seek your guidance on how to effectively configure TeX Live to work within the VS Code environment.
>>
>>
>> I would greatly appreciate any insights or recommendations you could provide to facilitate a smoother integration process. Your assistance would be invaluable in helping me and others who prefer VS Code as their development environment to utilize TeX Live more effectively.
>>
>>
>> Thank you for your time and support.
>>
>>
>> Best regards,
>>
>> Ignacio