Hi Keita,
Ikumi Keita <ik...@ikumi.que.jp> writes:
> However, I realized that ConTeXt support doesn't work at all. The reason
> is that `ConTeXt-add-environments' is broken as well as context.el
> doesn't use `ConTeXt-environment-list' correctly.
Thanks for looking at this.
> I figured out that `TeX-auto-add-type' is responsible for the failure of
> `ConTeXt-add-environments'. It adds entries in `TeX-auto-parser' in a
> form like
> ("environment" ConTeXt-auto-environment ConTeXt-add-environments
> ConTeXt-environment-list ConTeXt-environment-changed)
> , where "environment" is used as a key to extract each component from
> the entry. However, this entry conflicts with another entry
> ("environment" LaTeX-auto-environment LaTeX-add-environments
> LaTeX-environment-list LaTeX-environment-changed)
> , which shares the same "environment" as a key.
>
> Thus I propose to apply the attached second patch to make the key to be
> unique.
I'm not familiar with context.el, and most notably I don't know how much
context.el relies on functionalities provided by latex.el in order to
run, but can we de-couple them? If it is feasible at all, maybe we
should go that way for a possibly cleaner solution.
WDYT?
Best, Arash
