New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extra setting for adding supported languages (to allow for snippets being inserted other file types) #2520
Comments
Out of the scope of the extension. |
Hum, we already have some support for LaTeX fenced inside |
I am against supporting completions for LaTeX fenced block on our side. It should be treated as a language embedded in Markdown language. See: Markdown language extensions should take control of it. If they forward requests to LaTeX Workshop, our codes will be called appropriately. |
I fully agree. My point is precisely to investigate why it does not already work this way. We already provide support for LaTeX embedding in Markdown, but is seems limited and it should not be. |
Markdown language extensions have to call |
I use a setup where I write in Markdown and use Pandoc to either create PDF's directly or create tex-files.
For advanced stuff (like equations) I insert LaTeX directly in my Markdown files. It would be nice if LaTeX-Workshop would allow for the snippets to be inserted in documents that do not have a .tex extension. And the on-the-fly previewing of equations (and/or the Math Preview Panel) to work as well on those snippets.
I took a look at the code, and the snippet insert only works if
hasTexId
returns true. Currently it does so if thelanguageId
of the current document is one of the following: tex, latex, latex-expl3, doctex, jlweave, rsweaveI am suggesting a new setting that allows for an array of strings where you can add language ids that should also make
hasTexId
return true.I would definitely be willing to do this myself if there is support for such a feature.
The text was updated successfully, but these errors were encountered: