Unable to move a file without a specific fern error with getcurpos

[nickjj]

I don't know when this started to happen because I only update plugins once in a while but I can say about 4-5 months ago this wasn't an issue. My environment hasn't changed, this is with Vim 8.1 running within WSL 2. I've been using the same fern configuration as I had for years.

When I select a file within fern and try to move it:

• It prompts me to input the source and destination within Vim's command window where everything is filled out already and I'm expected to provide the new destination path (this is normal)
• I type the new file name and hit enter (this is normal)
• It throws the error below (this is unexpected):

Error detected while processing function <lambda>961[1]..<SNR>204_show:
line   33:
E118: Too many arguments for function: getcurpos
Press ENTER or type command to continue
1 items are moved
Press ENTER or type command to continue

Any thoughts on where to go from here?

[lambdalisue]

It seems this line cause that issue https://github.com/lambdalisue/fern.vim/blob/main/autoload/fern/internal/drawer/hover_popup.vim#L66-L66

I need to find which Vim version add an optional argument to the getcurpos. If that is added after Vim 8.1.2269, I'll label it as a bug.

[lambdalisue]

vim/vim@99ca9c4

Found it. So it was introduced from 8.2.1727 so Vim that fern support should have that feature. Do you use Vim order than 8.1.2269?

I'm sorry I think I'm horrible for math 😇 Fern should support 8.1.2269~8.2.1726 so this is a bug.

[nickjj]

Wow nice detective work. By the way I am using Vim 8.1.2269.

Edit, here's the full version information:

VIM - Vi IMproved 8.1 (2018 May 18, compiled Apr 15 2020 06:40:31)
Included patches: 1-2269

[lambdalisue]

@nickjj Could you try #460?

[nickjj]

Thanks, #460 is working.

I installed and updated fern like this: Plug 'lambdalisue/fern.vim', { 'branch': 'fix-getcurpos' }

Then I performed the same steps as reported in this issue and in the last case, it renamed the file successfully without an error. I performed the test on both a file and directory.