Not creating symlink from wakatime-cli.exe to wakatime-cli-windows-386.exe

[alanhamlett]

          Now I have the same issue, but I have "wakatime-cli-windows-386.exe" instead of "wakatime-cli-windows-amd64.exe".

Like this:

If i rename the "wakatime-cli-windows-386.exe" file to "wakatime-cli.exe", when i restart nvim, it will be removed.

Originally posted by @ParadiseWitch in #147 (comment)

[alanhamlett]

@ParadiseWitch you're using 32bit Windows? On startup, vim-wakatime should download one of these releases corresponding to your OS, then create a symlink from ~/.wakatime/wakatime-cli.exe to ~/.wakatime/wakatime-cli-windows-386.exe. If the symlink fails, vim-wakatime tries moving the file to ~/.wakatime/wakatime-cli.exe instead.

[ParadiseWitch]

@alanhamlett No, 64bit.

[alanhamlett]

That's the problem... it's downloading 32-bit wakatime-cli and then it fails checking the current version with wakatime-cli.exe --version. If we fix 32/64 bit detection then it should start working.

[alanhamlett]

We use powershell to detect 32/64 bit on Windows in Neovim:

vim-wakatime/plugin/wakatime.vim

Line 234 in 018fa9a

let cmd = 'if ((Get-WmiObject win32_operatingsystem | select osarchitecture).osarchitecture -eq "64-bit") { Write "amd64" } else { Write "386" }'

We need to find why that powershell command is returning 386 instead of amd64.

[alanhamlett]

@ParadiseWitch can you try updating to the latest vim-wakatime and restart Vim?

It might have been fixed with 0d2efa2.

[alanhamlett]

Closing as fixed because no response.

[alanhamlett]

Also added ba4537e to help with this issue.