While there many ways to execute a compilation workflow, one method is to use “magic comments” at the top of a latex file.
No further configuration should be required, but see the manual if you have problems. tex file: Then open the VS Code settings, and search for autobuild to set the option Latex-workshop > Latex > Auto Build: Run to onSave. (Optional) If you wish to have the editor automatically compile and display the document when you save your.
With a new VS Code session, install the following extensions If you install MiKTeX, ensure you choose the “Always install missing packages on-the-fly” option MacOS and Linux users can also use use either MiKTeX or TeX Live
Typically Windows users would want MiKTeX VS Code has an outstanding LaTeX editing extension, which provides a good way to become comfortable with the tool and managing source code online.
] up will upgrade versions of your packages to the latest versions possible given the graph of compatibility used in each. ] st will show you a snapshot of what you have installed. Likewise, ] rm Expectations will remove that package. ] add Expectations will add a package (here, Expectations.jl) to the activated project file (or the global environment if none is activated). For example, these lecture notes use Project.toml and Manifest.toml - which you likely instantiated during installation after downloading these notebooks. This feature will let you reproduce the entire environment and, if a Manifest.toml is available, the exact package versions used for a project. ] instantiate (or using Pkg Pkg.instantiate() in the normal julia mode) will check if you have all of the packages and versions mentioned in the Project.toml and Manifest.toml files, and install as required.
Īs discussed, the Julia package manager allowed you to create fully reproducible environments (in the same spirit as Python’s and Conda virtual environments).Īs we saw before, ] brings you into package mode. To see this in action, within an external terminal we will open it using both methods, and then use ] st to see which project is activated and which packages are available.įirst, with julia -threads auto we see that the globally installed packages are available at first, but that the existing Project.toml and Manifest.toml in that folder are chosen after we choose ] activate. If you start the terminal without activating a project, you can activate it afterwards with ] activate. See the documentation on environments and the package manager for more. IJulia.jl to ensure Jupyter support) you should try to keep the packages in different projects separated. While there is a global set of packages available (e.g. in the gear icon at the bottom of the screenĪ key difference between Julia and some other package managers is that it is capable of having different versions of each package for different projects - which ensures all projects are fully reproducible by you, your future self, and any other collaborators.
To turn on,Įnsure you have a GitHub account, which will be useful for further lecturesĬhoose Turn On Settings Sync. While it is a personal taste, consider enabling the bracket colorizer by finding the bracketPairColorization setting.Ī key feature of VS Code is that it can synchronize your extensions and settings across all of your computers, and even when used in-browser (e.g. If you are on Windows, search for eol and change Files: Eol to be \n. Search for quick open and change Workbench > Editor: Enable Preview from Quick Open and consider setting it to false, though this is a matter of personal taste. In the settings, search for Tab Size and you should find Editor: Tab Size which you can modify to 4. Open the settings with > Preferences: Open User Settings (see above for opening the command palette with ).Īs a few optional suggestions for working with the settings,