Workaround, Make expansions trigger expansions

[jeanbellynck]

I'm doing functional analysis. I want to convert 'Coo' into 'C\infty' and this automatically into 'C^{\infty}'.
For this, I added the rule
{trigger: "C\infty", replacement: "C^{\infty}", options: "tA"},
but it doesn't work because the expansion does not trigger new checks.

My current workaround is to have the expansion "Coo -> C^{\infty}", but I'd prefer to have the intermediate step.

I realize that enabling this might cause some pretty big recursion problems. Are there any safe workarounds?

[superle3]

I'd recommend the workaround that you're currently using.

Not sure how much of a problem the recursion would be and I have hit this problem a few times already where the solution doesn't feel quite that elegant. But turning it on might have unintended consequences that are too hard to deal with.

When I have time (and motivation) I will add it as an experimental option or not depending how complex it would be but I don't it should be a problem. (Like 1-2 months I think.)

Like the option would be a number of how many recursions. Shouldn't affect performance that much? As most of the bottleneck is actually inserting the changes. (Like checking I think takes 0.5 - 5ms Vs inserting 70-200ms).

[jeanbellynck]

Ok, I'll use the workaround for now. I might add some more chained expansions. I'll try to find similar workarounds for those.
If this feature were to be implemented, I'd love to try it out.

And thank you for the work on the plugin! Configuring snippets is a lot of fun.