Closed nickdrozd closed 6 years ago
If it really should be there, perhaps a new stable version should be released? Or something like that?
Thanks, I'll look into that.
At the same time, I don't see anything strange going on: the stable version of ace-window
works fine with the stable version of avy
.
It would be nice for the unstable version of ace-window
to be compatible with the stable version of avy
. But is it OK if not always the case?
As a user you have some fall-back options:
(defun avy-mouse-event-window (&rest _))
.ace-window
to stable as wellavy
from stableI'll add a fboundp
check to ace-window
for the time being, until a new stable avy version.
Thanks, added fboundp
check. Sorry for the delay.
Thanks, that did it!
I went to rebase on master recently and discovered that I couldn't run
ace-window
. It kept telling me thatavy-mouse-event-window
was not defined. Looking into the problem, I discovered that that function was added toavy
in https://github.com/abo-abo/avy/commit/a0ce6a7558e48b2ae150042a3e3cd559ba26152c and introduced intoace-window
in https://github.com/abo-abo/ace-window/commit/5e733ff695062725d39acd241bf8b3c6efcc5447. I was running the MELPA stable version ofavy
(https://stable.melpa.org/#/avy), so indeed I did not have that function defined.I don't know if its introduction was intentional, since the commit message only mentions "minor changes". The code also seems a little strange to me:
If it really should be there, perhaps a new stable version should be released? Or something like that?