A way to integrate LaTeX, VS Code, and Inkscape in macOS.
- Abstract
- Disclaimer
- Setup For Typing Blasting Fast
- Drawing Like a Pro - With Inkscape
- Updates
- Credits
- Related Project
- Star History
I use
This setup is universal for VS Code users indeed. The only part that'll be macOS-specific is the Inkscape part (Inkscape-figures and Inkscape-shortcut-manager). While the first part can be replaced by super-figure (while I still prefer my setup, you can still try it out even if you're in macOS), and you can certainly achieve a similar result in Windows as in my Notes, the drawing speed will be slower without the shortcut manager. Just keep that in mind.
If you still don't know what to expect, please check out my Notes taken in this setup. Also, due to the VS Code recent update (1.76.1), we have the profile functionality available. Specifically, this is my current minimal profile for
Available: My website
Please look through the two blog posts above by Gilles Castel! They are incredible and worth spending your time to understand how all things work, and what's the motivation behind all these. I'm only mimicking his workflow, with a little patience to set up the whole thing in my environment. Show respect to the original author!
Before we start anything serious, just copy the keybindings.json and settings.json into your own keybindings.json and settings.json. Don't worry, I'll explain what they do later.
VSCode-LaTeX-Inkscape/VSCode-setting/keybindings.json
Lines 1 to 133 in 6c87739
VSCode-LaTeX-Inkscape/VSCode-setting/settings.json
Lines 1 to 915 in 4e4d364
Also, create a snippet file for
-
Press
shift+cmd+pto open the VS Code command. -
Type
snippets, and chooseSnippets: Configure Snippets. -
Choose
New Global Snippets file.... -
Enter
latexto create a new file. -
Paste the
latex.jsoninto that file.VSCode-LaTeX-Inkscape/VSCode-setting/Snippets/latex.json
Lines 1 to 14 in b98c215
First thing first, please set up your VS Code with
-
Download MacTex. This can be replaced by something more lightweight, but in my opinion, this doesn't really help much in terms of speed or wasting your disk. But if you want something like this, check out TeXLive.
-
Download LaTeX Workshop
-
Copy-pasting the following configuration file into your
settings.json"latex-workshop.latex.autoBuild.run": "onSave"
This will save your time by compiling your
$\LaTeX$ project whenever you save your file bycmd+s.
Now, we go through things one by one following Gilles Castel's blog post.
To achieve a similar result as in Gilles Castel's setup, there is an extension called vsc-conceal for VS Code. All the setup is in the setting.json, and since this setup is quite straightforward, I'll just give a snapshot to show how it looks in practice.
Note that I set the "conceal.revealOn" to "active-line", which is why you will see the source code in line 51. There are other options you can choose, see the original repo for details.
If you look around in the VS Code extension marketplace to find UltiSnips' equivalence, you probably will find Vsnips. But I'm not sure why this is the case, I can't figure out how to set it up properly. Hence, I find another alternative, which is HyperSnips. Please first download HyperSnips and just follow the instructions, copy latex.hsnips into $HOME/Library/Application Support/Code/User/globalStorage/draivin.hsnips/hsnips/, and you're good to go!
To modify this file, you can either go to this file in your finder or use the VS Code built-in command function. For commands function,
- Press
shift+cmd+spaceto type in some commands to VS Code. - Type
>HyperSnips: Open Snippet File - Choose
latex.hsnips
After doing this, you're all set. But a big question is, what exactly is a snippet?
A snippet is a short reusable piece of text that can be triggered by some other text. For example, when I type dm (stands for display math), the word dm will be expanded to a display math environment:
If you are a math guy, you may need to type some inline math like \(\), which is kind of painful. But with snippets, you can have
See? You just type fm (not the best choice here, but since im is a common prefix, so can't really use that as our snippet 🥲), and then your snippet not only automatically types \(\) for you, but it also sends your cursor between \(\)! With this, you can type something really fast:
Note that in the above demo, I use a very common snippet, qs for ^{2}.
As you can imagine, this can be quite complex. For example, you can even have something like this:
or this:
For the first snippet, I type table2 5, and then it generates a table with 2 rows and 5 columns. For the second one, I type pmat for matrix, and then type 2 5 to indicate that I want a 2 by 5 matrix, then boom! My snippets do that for me in an instant!
My snippet file includes commonly used snippets as suggested in the original posts, you can look into it to better understand how it works. And maybe you can create your snippets also! Here are some useful snippets for you.
In the recent update of HyperSnips, the context functionality is implemented, which is very useful, and you should understand how it works. If you look at the top of the snippet file, you will see
global
function math(context) {
return context.scopes.findLastIndex(s => s.startsWith("meta.math")) > context.scopes.findLastIndex(s => s.startsWith("comment") || s.startsWith("meta.text.normal.tex"));
}
endglobalAnd for some snippets, you will see context math(context) in front of which, e.g., the greater or equal snippet:
context math(context)
snippet `>=|(?<!\\)geq` "greater or equal to" A
\geq $0
endsnippetwhile some do not, e.g., the display math snippet:
snippet dm "display Math" bA
\[
${1}
\]$0
endsnippetBasically, the context specifies when the snippet will be triggered, and I define the function math(context) to determine when we are in the math environment. This is quite important since the official math(context) function for detecting math scope for
global
function math(context) {
return context.scopes.some(s => s.startsWith("meta.math")) && !context.scopes.some(s => s.startsWith("comment") || s.startsWith("meta.text.normal.tex"));
}
endglobalHowever, this leads to some problems. For example, sometimes, in the equation, I want to write
\[
x_n = x \text{ for some \(n\) large enough},
\]Such a case is fine since the math I want to write in the text scope is simple, just \(n\). However, in the current (and perhaps most popular) scope function, it happens that \(\text{ \( not in the math mode \) }\).
To overcome this, I write the following more generic version:
global
function math(context) {
return context.scopes.findLastIndex(s => s.startsWith("meta.math")) > context.scopes.findLastIndex(s => s.startsWith("comment") || s.startsWith("meta.text.normal.tex"));
}
endglobalSo, since the nested environment is ordered in the scope, this will always return the correct mode. Even better, there will be no undefined behavior since if the .findLastIndex can't find either, it will return -1 instead of something undefined, so everything is handled.
Unlike Gilles Castel's approach, there is an available extension out there for you to simplify your math calculation already! Please go check out Latex SYMPY Calculator. It works like follows:
Magic right? Let's set it up! First, please look at the installation document provided by Latex Sympy Calculator. After your installation, you can set up the keybinding for calculating the math expression. I use shift+e, where e stands for evaluating, to calculate so that it will append an equal sign and the answer right after your formula, just like above. If you want to avoid showing the intermediate steps of your calculation, you can use shift+r, where r stands for replacing, to directly replace the whole formula and give me the answer only. See the demo below:
This plugin is indeed more powerful than just this, see the documentation for detail.
Let's go to the last thing covered in Gilles Castel's post, correcting spelling mistakes.
Although my typing speed is quite high, I have typos all the time. So this is a must for me. And surprisingly, this is the hardest thing until now for me to set it upright. Let's see how we can configure this functionality in VS Code! There are three plugins we need:
-
multi-command: This is a very powerful extension, which allows you to do a sequence of actions in one shortcut. We will use this later on also, and that's the place it shines.
-
Code Spell Checker: This is a popular spelling checker out there that meets our needs.
-
LTeX: If you are bad at grammar like me, you definitely want to install to check some simple grammar mistakes for you. Although it's not as powerful as Grammarly, not even comparable, it's still a good reference for you to keep your eyes on some simple mistakes you may overlook.
There is an unofficial API for Grammarly, and the plugin can be found here. Though it's quite slow...
Here is a quick demo of how it works when typing:
Additionally, if you also want to correct your grammar error, I use the shortcut cmd+k to trigger a quick-fix for a general error.
You can skip this part if you don't want to know the working mechanism. But if you're interested, please follow! The following code snippet in
settings.jsonis responsible for correcting your spelling mistakes by just clickingcmd+l.{ "key": "cmd+l", "command": "extension.multiCommand.execute", "args": { "sequence": [ "cSpell.goToPreviousSpellingIssue", { "command": "editor.action.codeAction", "args": { "kind": "quickfix", "apply": "first" } }, "cursorUndo", ] } },Make sure that the curly braces above have a trailing comma, otherwise, VS Code will complain about it.
The working mechanism is as follows. When you press
cmd+l, the multi-command will do the following:
- Use one of the default function from cSpell's:
goToPreviousSpellingIssue, which jump your cursor on that spelling error word- Triggered a default editor action, with the argument being
quickfixto open a quick fix drop-down list, and choose thefirstsuggestion- Move your cursor back by
cursorUndoAnd likewise, the following code snippet is responsible for correcting grammar mistakes.
{ "key": "cmd+k", "command": "extension.multiCommand.execute", "args": { "sequence": [ "editor.action.marker.prev", { "command": "editor.action.codeAction", "args": { "kind": "quickfix", "apply": "first" } }, "cursorUndo", ] } },
Now, the first part is over. Let's go to the next truly beautiful, elegant, and exciting world, drawing with Inkscape.
For more examples, check out the original blog. Or for more figures I draw, you can check out Note.
One last thing is that I'll assume you have already installed VS Code Vim. While this is not required, if you don't want to use it, then you'll need to assign different keybinding. Anyway, you'll see what I mean until then!
A big question is, why Inkscape? In the original blog, he had already explained it. One reason is that although
You need to install Inkscape first. I recommend you install this in a terminal. I assume that you have your homebrew installed. Then, just type the following into your terminal:
> brew install --cask inkscapeFirst thing first, include the following in your preamble
\usepackage{import}
\usepackage{xifthen}
\usepackage{pdfpages}
\usepackage{transparent}
\newcommand{\incfig}[1]{%
\def\svgwidth{\columnwidth}
\import{./Figures/}{#1.pdf_tex}
}And to use it in your code, it's like the following:
\begin{figure}[H]
\centering
\incfig{figure's name}
\caption{Your caption}
\label{fig:label}
\end{figure}And then you're done! Also, the compilation time for this is shorter than you can ever expect. Let's get started then!
This assumes that your
LaTeX_project
├── main.tex
├── main.pdf
├── Figures
│ ├── fig.pdf
│ ├── fig.pdf_tex
│ ├── fig.svg
│ .
.Now, let's get into the fun part, i.e., setting up the shortcut for this.
This is a figure manager developed by Gilles Castel, and here is the repo. I recommend you follow the installation instructions there. Here are just some guidelines for you.
-
Install choose (specifically for macOS, rofi for Linux instead):
> brew install choose-gui -
Install fswatch:
> brew install fswatch -
Install the Inkscape figure manager:
> pip3 install inkscape-figuresAfter installing it, type
inkscape-figuresin your terminal to make sure you have corrected install it.
If you're using Linux and Vim, then you are done already. But since you're using macOS and VS Code, please follow me, there are some more things for you to configure.
If you're using Windows, then check out super-figure. It implements similar functionalities but in a more chunky way. Even if you're using macOS, you can try it too, although I prefer my setup.
Firstly, install the Command Runner. This will allow you to send commands into a terminal with the shortcut. The configuration is in settings.json, and we'll see how it works later. Now, this is a tricky part: you need to find the source code of the inkscape-figures manager. In my case, it's in /Users/pbb/opt/anaconda3/lib/python3.8/site-packages/inkscapefigures.
Using global finding may be helpful...
Open this directory by VS Code, there is something for you to modify. Ok, I know you probably don't have that much patience now, so I have a modified version available here. Just replace the whole directory with mine, and you're good to go.
Notice that the directory in this repo is named
Inkscape-figure-manager, while in your system, it should beinkscapefigures.
In Gilles Castel's approach, he uses the shortcut
ctrl+fto trigger this script, which will copy the whole line's content depending on the cursor's position, and the script will send the snippets by the functiondef latex_template(name, title): return '\n'.join((r"\begin{figure}[ht]", r" This is a custom LaTeX template!", r" \centering", rf" \incfig[1]{{{name}}}", rf" \caption{{{title}}}", rf" \label{{fig:{name}}}", r"\end{figure}"))to
stdout, and then create a figure by thename, which is the content of the line.But this in VS Code is impossible, hence we don't need this, we'll use command line. And if we leave this function as it was, then it will send all these snippets into our terminal, which is quite annoying. So the modified version just removes this snippet completely.
But let me explain it to you, in case you want to modify it to meet your need later on. First thing first, we see that in the given code in
keybindings.jsonandsettings.json, we're using Command Runner, so let me tell you how to set this up first.
We're now prepared to see a detailed explanation of commands provided in Inkscape figure manager. There are three different commands in the Inkscape figure manager. We break it down one by one.
Since Inkscape by default does not save the file in pdf+latex, we need Inkscape figure manager to help us. We need to first open the file watcher to watch the file for any changes. If there is any, then the file watcher will tell Inkscape to save the file in pdf+latex format.
To open the file watcher, you can type inkscape-figures watch in the terminal. But remember the Command Runner we just installed? We can assign this command with a keybinding! In my case, since I don't want to introduce more than one keybinding for Inkscape-figures manager, I use mode provided by vim to help us. In VISUAL mode (enter by v in NORMAL mode), press ctrl+f.
You should trigger this at the beginning. i.e., use this after you open your project folder. To check whether
watchis triggered correctly, you can simply open the terminal and see what's the output when you pressctrl+f: If it's already triggered, then it'll show> inkscape-figures watch Unable to lock on the pidfile.Otherwise it'll simply show nothing. (Remember to select the terminal corresponds to
runCommand!)
In
keybindings.json, we have{ "key": "ctrl+f", "command": "command-runner.run", "args": { "command": "inkscapeStart", "terminal": { "name": "runCommand", "shellArgs": [], "autoClear": true, "autoFocus": false } }, "when": "editorTextFocus && vim.active && vim.use<C-f> && !inDebugRepl && vim.mode == 'Visual'" }for starting the Inkscape figure manager. And the command is defined in
settings.json:"command-runner.commands": { "inkscapeStart": "inkscape-figures watch" }In detail, we just use Command Runner to run the command we defined in
settings.json, in this case, I explicitly tell the keybindingctrl+fwill triggerinkscapeStartwhen I'm inVISUALmode in Vim, which is justinkscape-figures watcheras defined above.Notice that we set the
autoFocus=falsefor the terminal Command Runner uses since we don't want a pop-up terminal to distract us. If you want to see whether the command is triggered correctly every time, you can set it totrue.
Same as above, we also use ctrl+f to trigger inkscape-figures create command. But in this case, we use INSERT for creating a new Inkscape figure. Specifically, we first type out the image's name we want our image to be called, then, in this case, we're already in INSERT mode, we just press ctrl+f to create this image after naming.
Detail Explanation
We set up our
keybindings.jsonas{ "key": "ctrl+f", "command": "extension.multiCommand.execute", "args": { "sequence": [ "editor.action.clipboardCopyAction", "editor.action.insertLineAfter", "cursorUp", "editor.action.deleteLines", { "command": "editor.action.insertSnippet", "args": { "name": "incfig" } }, { "command": "command-runner.run", "args": { "command": "inkscapeCreate", }, "terminal": { "name": "runCommand", "shellArgs": [], "autoClear": true, "autoFocus": false } }, ] }, "when": "editorTextFocus && vim.active && vim.use<C-f> && !inDebugRepl && vim.mode == 'Insert'" },and also in
settings.json:"command-runner.commands": { "inkscapeCreate": "inkscape-figures create ${selectedText} ${fileDirname}/Figures/" }We break down what
ctrl+fdo inINSERTmode exactly step by step. We see that when we pressctrl+finINSERTmode, we triggermultiCommand.executeto execute a sequence of instructions, which are
- Copy the content into your clipboard of the line your cursor at
- Insert a blank line after since we need to insert a snippet, and that will delete an additional line. You can try to delete this and the next instruction, and see what happens.
- Move back our cursor after inserting that new line.
- Delete that copied content by removing this line.
- Insert a snippet defined in
latex.json. Notice that this is the default snippet functionality built-in VS Code, not HyperSnips we have used before. I'll explain where to copy this file in a minute.- Lastly, we send a command in a terminal by Command Runner, with the command
inkscapeCreatewe defined insettings.json.In the fifth instruction, the snippet we used is
VSCode-LaTeX-Inkscape/VSCode-setting/Snippets/latex.json
Lines 1 to 14 in b98c215
which is just the snippet we remove from Inkscape figure manager's source code! It's back again, in a different approach.
Let me break it down for you. Firstly, I changed into INSERT mode in VS Code Vim and typed my new figure's name figure-test. Then, I press ctrl+f to trigger the keybinding, which will automatically create an Inkscape figure named figure-test for me and open it.
The three files will be created along the way:
figure-test.pdf,figure-test.pdf_texandfigure-test.svg. Unfortunately, to rename a file, you'll need to manually rename three of them.
Again, we also use ctrl+f to trigger inkscape-figures edit command, but this time in NOMAL mode. Here, choose comes into play. After you select the image you want to edit in Inkscape, you simply press enter and it'll open that image for you to edit.
You can modify the styling of choose. For example, in
picker.py, we have the following:def get_picker_cmd(picker_args=None, fuzzy=True): """ Create the shell command that will be run to start the picker. """ if SYSTEM_NAME == "Darwin": args = ["choose"] # args = ["choose", "-u", "-n", "15", "-c", "BB33B7", "-b", "BF44C8"]We see that we don't have any additional argument for
choose, but if you want, you can replace this line by the next line, which modify the style ofchoose. For detail information, typechoose -hto see all the options.
The corresponding keybinding in 'keybindings.json' is:
{ "key": "ctrl+f", "command": "command-runner.run", "args": { "command": "inkscapeEdit", "terminal": { "name": "runCommand", "shellArgs": [], "autoClear": true, "autoFocus": false } }, "when": "editorTextFocus && vim.active && vim.use<C-f> && !inDebugRepl && vim.mode == 'Normal'" },and also in
settings.json:"command-runner.commands": { "inkscapeEdit": "inkscape-figures edit ${fileDirname}/Figures/" }I think now it's clear enough how all these work together to trigger the corresponding command. When you press
ctrl+finNORMALmode, you'll trigger theinkscape-figures editcommand, and it'll look into yourFigures/subfolder to see what figures you have and pop out a window for you to choose, which is the functionality provided by choose.
In the following demo, I create another figure named figure-test2, then modify it a little, and compile it again.
In this section, we'll set up a very efficient shortcut manager to help you draw any mathematical figures faster than you can ever imagine! Notice that this setup is quite complicated, but the result is quite good. It depends on
- Hammerspoon: For windows focus.
- Karabiner Elements: For capturing the overlapping key chords.
Please download the above two apps.
We'll need Karabiner Elements' Complex Modifications to help us. The steps are the following (adapted from ️⌨ How to type?).
- Open Karabiner-Elements, go to Misc and click on Export & Import.
- Copy
Inkscape.jsoninto.config/karabiner/assets/complex_modifications.
- Again open Karabiner-Elements, go to Complex Modifications and click on Add rule.
- Enable it.
If you're interested in how Inkscape.json is created, see the following.
Detail Explanation
The Inkscape.json is created by using a jsonnet file. The file can be found here,
and the jsonnet tool can be installed via > brew install jsonnet.
Converting the jsonnet file into the json file for Karabiner Elements can be done as follows
> jsonnet karabiner-Inkscape.jsonnet > ~/.config/karabiner/assets/complex_modifications/karabiner-Inkscape.jsonFirstly, open the Hammerspoon console and run hs.ipc.cliInstall() to install the cli command hs. Then, just add the following code to your ~/.hammerspoon/init.lua.
As a reference for the key chords, I added the original picture from the original blog but with the key chords included in the picture.
I did not add the ergonomic rebinding x, w, f, and shift+z. This should be possible in Inkscape itself. This setup also misses the bindings t, shift+t, a, shift+a, s, and shift+s. Since I encountered issues I did not pursue these.
This is the whole setup I have, and let's wrap this up since I know this may be quite overwhelming.
- Before you start your project, enter the
VISUALmode by pressingvinNORMALmode. And then pressctrl+f. This will set up the file watcher. - When you want to create a new figure, go into a new line, type the name of your figure in
INSERTmode, then pressctrl+f. This will create a new figure with the name you typed, and open it in Inkscape for you. - When you have drawn your figure, as long as you press
cmd+sin Inkscape, it will automatically save the figure inpdf+latexfor you, then you can close Inkscape. - When you want to edit one of your figures, you press
ctrl+finNORMALmode, it will pop out a window for you to choose the figure you want to edit. And the rest is the same as 3.
After some research, although there is a way to let the original script in inkscape-shortcut-manager run correctly since it depends on xlib, which is no longer used by macOS for almost every application(including Inkscape, as expected), hence the only thing I can do now is to give up. In a perceivable future, if I have time to find an alternative way to interrupt the window activity in macOS, I'll try to configure it for macOS.
Now the Inkscape Shortcut Manager is fully functional, see here.
I have been working on Category Theory for a while, and I found out that quiver is quite appealing, hence I integrate it into my workflow. You can also pull it to your local environment, configure the VS Code Task, and combine it with a hotkey to use it locally. Specifically, I added the following code to my keybindings.json:
{
"key": "ctrl+c",
"command": "command-runner.run",
"args": {
"command": "quiver",
"terminal": {
"name": "runCommand",
"shellArgs": [],
"autoClear": true,
"autoFocus": false
}
},
"when": "editorTextFocus"
},and also, define the command quiver as
"command-runner.commands": {
"quiver": "open -na 'Google Chrome' --args --new-window <path-to-quiver>/quiver/src/index.html"
},Notice that you'll need to build it first if you want to use it offline! Please follow the tutorial here. Otherwise, it's totally fine to use "quiver": "open -na 'Google Chrome' --args --new-window https://q.uiver.app/" as your command.
This is what the workflow looks like.
To use the package tikz-cd, you need to include the following in your header:
% quiver style
\usepackage{tikz-cd}
% `calc` is necessary to draw curved arrows.
\usetikzlibrary{calc}
% `pathmorphing` is necessary to draw squiggly arrows.
\usetikzlibrary{decorations.pathmorphing}
% A TikZ style for curved arrows of a fixed height, due to AndréC.
\tikzset{curve/.style={settings={#1},to path={(\tikztostart)
.. controls ($(\tikztostart)!\pv{pos}!(\tikztotarget)!\pv{height}!270:(\tikztotarget)$)
and ($(\tikztostart)!1-\pv{pos}!(\tikztotarget)!\pv{height}!270:(\tikztotarget)$)
.. (\tikztotarget)\tikztonodes}},
settings/.code={\tikzset{quiver/.cd,#1}
\def\pv##1{\pgfkeysvalueof{/tikz/quiver/##1}}},
quiver/.cd,pos/.initial=0.35,height/.initial=0}
% TikZ arrowhead/tail styles.
\tikzset{tail reversed/.code={\pgfsetarrowsstart{tikzcd to}}}
\tikzset{2tail/.code={\pgfsetarrowsstart{Implies[reversed]}}}
\tikzset{2tail reversed/.code={\pgfsetarrowsstart{Implies}}}
% TikZ arrow styles.
\tikzset{no body/.style={/tikz/dash pattern=on 0 off 1mm}}You can certainly follow my Template, which already includes all the requirement headers for you.
Now, instead of using HyperSnips for Math, we're using HyperSnips, namely the original one! Since I just found out that we can trigger the snippets only in math mode by using the special keyword called context, I migrated to the original one. To migrate, you just need to uninstall HyperSnips for Math, install HyperSnips with the updated latex.hsnips I prepared for you, and then enjoy!
I finally have time to document the configuration of the Inkscape shortcut manager and make some changes to make this document more readable. Personally, I have used this workflow for more than half of a year, so I think this is stable and will not be changed shortly.
Again, thanks to Gilles Castel, this workflow fits my style. Although it originally worked in Linux+Vim only, the idea is the most important thing. Without his wonderful post, I can't even imagine this is possible. But now it is! Go to his original post to show him some love.
- LaTeX-Template
- Notes
- gillescastel/inkscape-figures
- gillescastel/inkscape-shortcut-manager
- chipsenkbeil/choose
- varkor/quiver