Hi Kyle, Kyle Meyer <k...@kyleam.com> writes:
>> I just have one concern, which is pretty theoretical. Isn’t it bad to >> define the alias to be font-lock-ensure since this is an existing function >> and people would have clear expectations of what they are calling? I >> realize that there’s no Emacs-25 that will not have this function (which >> is why it’s very theoretical). > > I agree, but, like you, I'm not sure it will matter in practice. Again, > this was the solution that was already in Org's repo at the time I > backported Emacs's 6711a21f1. However, it's easy enough to switch to > using an org-font-lock-ensure variant that avoids these issues, so I > will do that (in an updated patch and on Org's maint). Thanks. Kyle Meyer <k...@kyleam.com> writes: >> However, it's easy enough to switch to using an org-font-lock-ensure >> variant that avoids these issues, so I will do that (in an updated >> patch and on Org's maint). > > I've attached updated patches against emacs-25. If these are applied to > the Emacs repo, I'll backport the new font-lock-ensure alias to Org's > maint. Looks good, thanks. Rasmus -- Er du tosset for noge' lårt!
