Ihor Radchenko <[email protected]> writes:

> Christian Moe <[email protected]> writes:
>
>> : (setf (alist-get "ang" org-entities nil 'remove 'equal) nil))
>>
>> Note that the "ang" entry is redundant; the =\angle= entity exports to
>> exactly the same result, an angle symbol. So if siunitx is popular and
>> this conflict is going to crop up often, perhaps we should consider
>> removing the "ang" entry in org-entities. It would be a breaking change
>> for a few users, though.
>
> It might be redundant for latex export, but not for html or ascii.

Well, the definitions of "ang" and "angle" in org-entities are identical
for all export backends:

     ("ang" "\\angle" t "&ang;" "[angle]" "[angle]" "∠")
   ("angle" "\\angle" t "&ang;" "[angle]" "[angle]" "∠")

But there's no *conflict* with other backends, and for latex a
conflict arises only with a particular package, which is not something
we can generally guard against. Anyway, I don't think we guarantee that
latex commands will work outside a latex environment of some kind. And
as I've belatedly added to my reply, the obvious solution =\(\ang{90}\)=
only requires a few extra keystrokes. So no, there's not much of a case
for making a breaking change.

Yours,
Christian

Reply via email to