Kyle Meyer writes:
> Basil L. Contovounesios writes:
>> How involved would it be to make org-eldoc work in
>> non-"backwards-compatibility" mode?
>
> I think we can do that, while still supporting Org's minimum Emacs
> version, by following python.el. Here's what it does:
> ...
>
> ... org-eldoc
Basil L. Contovounesios writes:
> "James N. V. Cash" writes:
>
>> This patch makes it continue to work by setting the new variable
>> eldoc-documentation-strategy, which puts eldoc in
>> "backwards-compatability" mode.
>
> How involved would it be to make org-eldoc work in
> non-"backwards-compat
"James N. V. Cash" writes:
> This patch makes it continue to work by setting the new variable
> eldoc-documentation-strategy, which puts eldoc in
> "backwards-compatability" mode.
How involved would it be to make org-eldoc work in
non-"backwards-compatibility" mode?
> From 5c04048c0d1ed3f80c7dd
Nicolas Goaziou writes:
> Do we need another variable for that? Could
> org-eldoc-documentation-function catch wrong-number-of-arguments error,
> and try another call instead?
I believe that the issue is org-eldoc-documentation-function itself is
called with the wrong number of arguments; the
Hello,
"James N. V. Cash" writes:
> In Emacs 28, eldoc now passes in a callback to the documentation
> functions. This breaks org-eldoc as it currently is, as
> org-eldoc-documentation-function gets called with the wrong number of
> arguments.
>
> This patch makes it continue to work by setting
