Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Latex using $ delimitors

A topic by SekoiaTree created Oct 18, 2021 Views: 314 Replies: 10
Viewing posts 1 to 5

Integrated latex sometimes uses $ as a delimiter. I already have some notes in this format, and it'd be great if I could use it (especially since writing ```latex is unwieldy, particularly to take notes for classes..). Alternatively, custom delimiters would be great.

$ is generally for inline math, and $$ makes a new centered line with just the math.


Thanks!

(1 edit)

Thanks for the feedback!

So, I’ve avoided adding $ and $$ for a couple of reasons;

I think that backticks are just better for this, since they already indicate changing the current “mode” while writing, and the dollar character itself is both arbitrary, and is much more likely to be used in both technical and non-technical writing.

It’s also more expensive to parse out a new delimiter just for math/latex than it is to re-use the existing backtick ones.

That all said, $/$$ is much more common, and should be supported for portability. If I can add them to the parser without too much impact, I’ll add them along with a separate setting to enable them.

That's great, thanks!

Also, as a heads up: There are a lot of different supported syntaxes for math, since it’s very non-standard, so it’s very likely that, whatever shorthand format Deepdwn adopts, somebody will be left out.

fair enough, but it seems like most of those are just delimiters? So either there could be custom delimiters, or people can just find/replace if they want to adapt it

(+1)

$ and $$ Latex delimiters were added in v0.29

Awesome, thanks! I can't seem to make them work though... There's just no highlighting or anything, and neither the preview nor the exports show anything other than the standard characters. Am I missing something?

The formats I tried:

$test$

$ test $

`$ test $`

$latex test $

$` test `$

(+1)

Sorry about that! It looks like this feature got lost in the release shuffle. It’s scheduled to go out in the next minor update.

alright, thanks!

(+1)

Sorry for the mixup. This was released in v0.30

awesome, thanks!