#1

Related to but not identical to:

Try adding this to a note

$$
\wedge = \text{and} \\
\lor = \text{or} \\
\lnot = \text{not}
$$

Should render this:
image

But instead renders this:
image

Why don’t newlines work?

MacOSX
v0.10.13

2 Likes
#2

Decent workaround for now is to split into multiple Latex sections:

$$
\wedge = \text{and}
$$
$$
\lor = \text{or}
$$
$$
\lnot = \text{not}
$$

Result:

image

#3

It’s not related to that bug at all. It’s another upstream problem

#4

Related in terms of similar output appearance, not cause.

Anything I can do to speed along upstream problems?

#5

The upstream bug is the cause of this issue. It’s scheduled to be patched in Q2 2021 according to the MathJax developers, and in the meantime you can use \displaylines{....} to wrap the whole thing as a temporary workaround.

1 Like
#6

I don’t see why this should be a bug in the first place. This seems to be normal LaTeX behaviour to me. If you type

$$
\wedge = \text{and} \\
\lor = \text{or} \\
\lnot = \text{not}
$$

into a LaTeX document, you get the same result that you get in Obsidian – everything is on a single line. If you want to have multiple lines you have to use \displaylines{...} as Licat says (or \begin{gathered}... \end{gathered}). If you want to have the equations to align, then you need to use the aligned environment instead:

$$
\begin{aligned}
\wedge &= \text{and} \\
\lor &= \text{or} \\
\lnot &= \text{not}
\end{aligned}
$$
1 Like
#7

The linebreak issue seems still not working (version 0.13.14 windows), any progresses about this issue? (p.s. mathjax seems have already fixed this bug testing page MathJax Dynamic Math Test Page)

#8

that’s not the official mathjax 3 demo and the bug is still open upstream.

#9

Thanks for the replay. Hope the upstream will fix it soon.

#10

Seems to still be broken for version v0.13.23. :cry:

#11

I don’t think it is broken, you should just use the aligned environment (in Mathjax and LaTeX), which is already shown with an example in a reply above.

#12

Ahh, ok. I assumed the aligned environment was a workaround.
Using it now, works fine, thanks. :+1: