On Wed, Aug 5, 2020 at 11:57 AM Jeong Dal wrote: > Dear Mikael, > > > 2) Is there a nice way to compile the tex file from > > within vs code? As of > now, I opened a terminal and compiled from that, but that feels like the > wrong way of doing it. > > > For the first question, I don’t know either. > For the second question, I’d like to explain what I did for compiling TeX > file in vscode. > Since I use vscode in MacOsX, you may find your way in Linux. > > There is a tasks.json file in .vscode folder. > I added the following script in the “tasks":[ ] and save it. > (You have to modify the "texmf-osx-64/bin” path in the following script > from your machine. > > { > "label": "ConTeXt LuaMetaTeX", > "type": "shell", > "command": "export > PATH=/Users/graph/ConTeXtLM/tex/texmf-osx-64/bin:$PATH;mtxrun > --autogenerate --script context --autopdf --purge '${file}'", > "args": [], > "options": { > "cwd": "${fileDirname}" > }, > "group": { > "kind": "build", > "isDefault": true > } > }, > > When you want to compile a ConTeXt file, find “terminal > Run Build task” > in the menu, > then “ConTeXt LuaMetaTex” will pop up. > Or just use the key “command-shift-B” instead using menu item. > > I hope that it may help. > > Best wishes, > > Dalyoung > > ___________________________________________________________________________________ > If your question is of interest to others as well, please add an entry to > the Wiki! > > maillist : ntg-context@ntg.nl / > http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : http://contextgarden.net > > ___________________________________________________________________________________ > Dear Dalyoung, Thanks! That got me up and running. Maybe this can help others (or maybe it is well-known): * Since January, the editor supports a global tasks.json file (if I understood https://stackoverflow.com/questions/41046494/making-global-tasks-in-vs-code correctly). I updated, and indeed, that seems to work. * I noticed that valid macros are recognized while typing, even if one has not used them before. When one starts typing the text is non-bold, and when it is a known macro it gets bold. That was useful. Best regards, Mikael