You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The command definitions will be available in the current file (and in fact, leaking to the whole obsidian app once this block is rendered, which could be a security issue).
Feature Request
It would be helpful to support macro definitions, for example in the page's md preamble:
---obsidian-latex-suite:
latex-preamble: | \newcommand{\diff}[2]{\frac{\mathrm{d}#1}{\mathrm{d}#2}} \newcommand{\pardiff}[2]{\frac{\partial{}#1}{\partial{}#2}} \newcommand{\ie}{\textit{i}.\textit{e}.}---$$\ie \diff{E}{u} = \pardiff{L}{u} - \diff{}{x}\pardiff{L}{u'} = 0 % the commands are available ONLY IN THIS FILE.$$
Or setting them in some global config file so that all the files in the vault will benefit:
// .config/obsidian-latex-suite.conf.js{// ...'latex-preamble': ['\newcommand{\diff}[2]{\frac{\mathrm{d}#1}{\mathrm{d}#2}}','\newcommand{\pardiff}[2]{\frac{\partial{}#1}{\partial{}#2}}','\newcommand{\ie}{\textit{i}.\textit{e}.}'],// all the docs will be able to use these commands.// ...}
The text was updated successfully, but these errors were encountered:
The focus of this plugin is making typing LaTeX easier, as opposed to extending its functionality. Therefore, I think this functionality would belong better in the Extended MathJax plugin that you mentioned.
The command definitions will be available in the current file (and in fact, leaking to the whole obsidian app once this block is rendered, which could be a security issue).
Maybe this can be brought up as an upstream issue in Obsidian?
Motivation
Currently, I define custom latex commands inside the first displayed equation block, for example:
The command definitions will be available in the current file (and in fact, leaking to the whole obsidian app once this block is rendered, which could be a security issue).
Feature Request
It would be helpful to support macro definitions, for example in the page's md preamble:
Or setting them in some global config file so that all the files in the vault will benefit:
The text was updated successfully, but these errors were encountered: