Finding error in LaTeX document on Visual Code - visual-studio-code

I was wondering if there was an easier way of finding an error in the LaTeX document written using Visual Code. Its sometimes the case that there would be an error, such as a missing $ or {} or something similar, and unlike TeXWorks, VS won't show the exact nature of the error. It could be that I am missing something in the output panel.

Related

Scala in VSCode: error highlighting not working

I want to use VSCode to work on Scala code, but cannot get error highlighting to work.
See some example code below, how it looks like, vs. how I want it to highlight errors.
I think every proper programming language should have code editor support for highlighting of obvious errors regarding undefined variables, functions or operator overloadings.
What can I do, to get error highlighting for Scala in VSCode?

Where does VSCode store files related to markdown codeblock syntax highlighting?

I'm trying to find the files necessary to add my own syntax highlighting to fenced code blocks in a markdown document within Visual Studio Code. e.g.
```Python
# Comment
print("hello world")
```
will provide syntax highlighting for Python. I'm trying to add syntax highlighting for an unsupported language.
I have tried to find these on my own, but it's been all guesswork. I've found what looks like related files under C:\Users<user>\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions. There's a markdown-basics folder within there that contains a syntaxes\markdown.tmLanguage.json that appears to contain fenced code block references, but not the actual syntax definitions. There's also folders for a variety of languages. Trying to create a new definition based on these doesn't seem to work though.
I would appreciate any help figuring out how fenced code block syntax is defined.

How can I print the output of each line in an .ml file

I have an .ml file and I want to be able to run it line-by-line as if I was typing it in the top-level ocaml interpreter
The problem is, if I simply type "ocaml file.ml" in the terminal, I don't get the output from the REPL, and I can't debug and compile it, since it contains the #use directive.
I've tried using several different extensions for Visual Code, but none of them worked for me.
Is there anything I can do to simply be able to run the file and get the output from the ocaml REPL?
Thanks.
I never used VS Code (if you are referring it as 'Visual Code'), but SLIME in emacs or its Vim version of it is probably what you want.
Based on that, I tried searching for an VS Code extension that does works like SLIME: SendToREPL.
(Disclaimer: the author claims it works for Python, Node, and reply (not sure what it is though), but I am quite confident that it will work for OCaml REPL/UTop.)

Syntax highlight for APIDoc/JSDoc in VS Code

I'm using APIDoc to document my server side APIs.
I do so in separate .js files that are hundreds of lines long so syntax highlighting could be helpful.
It should probably look something like this.
Before writing a custom syntax highlighter I want to make sure I'm not missing anything though - is there a way to highlight APIDoc/JSDoc syntax already (something like this for Atom)?
Thanks!

"Error in syntax_table logic for to-the-end intervals" error in emacs

I use emacs for most online text editing, for PHP and javascript files especially. "PHP Abbrev" seems to be the mode for PHP files?
Lately I've been getting this error a lot within emacs, for a specific file:
"Error in syntax_table logic for to-the-end intervals"
The file is upwards of 5000 lines of PHP functions only, with no syntax errors, and runs well.
Yet sometimes (not always) I get that error, which seems to imply some sort of balancing issue. The worst part is that it prevents me from typing things like { } brackets, and I can't even write the code I need. Sometimes I need to code within comment brackets for it to allow it, then remove them at the end.
Is there any way to bypass this somehow, or detect if there is actually a balancing issue somewhere?