This is not necessarily an issue with cdlatex itself, rather I think a problem with recent changes in org mode itself which seem to break cdlatex a bit.
With older org mode (e.g. 9.6.30), typing a single dollar would be enough to indicate "we are entering math now" and so cdlatex expansions would work, e.g. typing
$fr<TAB>
would expand to
$\frac{}{}
with point inside the first pair of curly brackets. With more recent org mode (e.g. 9.7.11) this no longer works, <TAB> does nothing. I have tried this with a minimal init file (only loading auctex and cdlatex) so I am confident it is not the result of some other weird customisations of mine (although you never know). The same thing happens if instead I type
\(fr<TAB>
but things are fine in more structured environments like align, etc. I am guessing it is something to do with org--math-p or some such.
My question is: are you aware of this issue? Can you replicate it? Is there a workaround, or are you aware of plans (in the org team) to make changes which fix this? I know I should probably also raise this with the org team but I wanted to check with you first.
Much thanks,
Michael
This is not necessarily an issue with cdlatex itself, rather I think a problem with recent changes in org mode itself which seem to break cdlatex a bit.
With older org mode (e.g. 9.6.30), typing a single dollar would be enough to indicate "we are entering math now" and so cdlatex expansions would work, e.g. typing
$fr<TAB>would expand to
$\frac{}{}with point inside the first pair of curly brackets. With more recent org mode (e.g. 9.7.11) this no longer works,
<TAB>does nothing. I have tried this with a minimal init file (only loading auctex and cdlatex) so I am confident it is not the result of some other weird customisations of mine (although you never know). The same thing happens if instead I type\(fr<TAB>but things are fine in more structured environments like align, etc. I am guessing it is something to do with
org--math-por some such.My question is: are you aware of this issue? Can you replicate it? Is there a workaround, or are you aware of plans (in the org team) to make changes which fix this? I know I should probably also raise this with the org team but I wanted to check with you first.
Much thanks,
Michael