todo.org

Todo

Do it now

cdlatex accents

And use the accent engine to make the abar -> \bar{a} style snippets.

Decide what cdlatex snippets to keep

Decide syntax for power

Needed expansions: ^i, ^j, ^ij, ^k, ^n, and maybe +1 versions too

Options

We only need to consider collisions with words that start with 1 alphabet letter and then one of these expantions, see regexes.

p prefix

pi, pj, pn. Matching regex: ^[A-Za-z]p[ijkn]

p postfix

ip, jp, np. Matching regex: ^[A-Za-z][ijkn]p

check regexes against English words

Try to find how to generate undo entries

So users can easily undo expansions. Maybe even bind DEL in a transient map after expansions to undo expansions.

Look at buffer-undo-list and how smartparens does it.

Org table <-> elisp code pipeline

The table -> code is preferable I think. Currently we have code -> table but we’d need to separate into separate vars holding snippet list source in order to format it to separate tables.

Yasnippet expansions

Store the snippets source in a list/hashmap instead of separate files.

Smart frac

Finer grained subscripts

So a_11 becomes a₁₁ - essentially you’d write a11 to get the subscripts.

In consideration

Stricter condition for some cases?

Sometimes texmathp isn’t enough. Too many words contain the letters “to” to have it expand to \to unconditionally in maths.

Snippets for envs?

I’m not sure how much better we can do in this case compared to just yasnippet.

Separating the engine from snippets

The Yasnippet route