Closed Shane-XB-Qian closed 2 years ago
This is caused by a bug in the Vim9 import support (recent changes made to the Vim9 import feature). I have pushed 85417435fafc78c09d5a445690afe87210b3b7d7 to workaround this problem. Let me know if this addresses this issue.
This Vim bug has now been addressed by patch 8.2.4063 (https://github.com/vim/vim/commit/b8822442d716df0230c79531132e530e95cc17e3).
I have pushed 8541743 to workaround this problem. Let me know if this addresses this issue.
yes, that patch can workaround this issue. // thx. that vim9script 'import' refactor caused lots change...
recently vim and this changed much, not some err not very sure what happened... :-)