Dear Christian -- Thanks for your reply. My question evolved.
Christian Moe <[email protected]> writes: > : (setf (alist-get "ang" org-entities nil 'remove 'equal) nil)) This snippet works perfectly for me with the e:t option. It seems that e:nil doesn't just turn off entity translation, it also apparently turns on control character escaping. That is with e:nil, "\ang{90}" exports to "$\backslash$ang\{90\}" This surprised me, I assumed in the moment that this kind of escaping always happens unless a macro is specifically protected. I figured \num and company were popular enough to get this treatment by default. Now, the question is why e:nil works that way. I suppose it's meant to support exporting "\windows\path" ? But that's the only example I can think of, and it's not a very good one. > the obvious solution =\(\ang{90}\)= only requires a few extra > keystrokes. This is my usual approach, I recently wrote a document with very many specific angle declarations, often in tables. It was somewhat annoying to put them in a math environment with respect to widening my table columns and slowing down heading-wide latex previews. @@latex:\ang{90}@@ would have at least made previews more convenient, but greatly widened the columns, hence my question. > So no, there's not much of a case for making a breaking change. I agree this is not the kind of thing to put upstream. I'll enjoy my new configuration though. I'll have plenty more angles to typeset soon.
