Closed opti21 closed 2 years ago
Just had to remove the ~/.wakatime folder and reinstall
If it happens again, please share the contents of your .wakatime folder since this might still be a bug.
@alanhamlett Ooh fun I managed to get this as well, "$HOME.wakatime\" has only "vim_shared_state" and "wakatime-cli-windows-amd64.exe", so maybe some weird windows thing deleting the "wakatime-cli.exe" symlink or not creating the symlink correctly with Plug or Packer or what have you.
seems like it doesn't have anything to do with wakatime plugin. God knows what happened. The error is just misleading, that's about the only thing I think can be fixed.
Removing $HOME/.wakatime
wasn't enough on a particular system I use. I also had to manually change the file permissions to give myself rwx
access:
chmod 771 $HOME/.wakatime
BTW, perhaps you can get away with lower permissions for group and others (my local machine has 751 on that folder, for example).
Same error here. After removing .wakatime
, you may still need to create the folder manually to solve the privilege problem: mkdir .wakatime
Error detected while processing function68_SendHeartbeats:
line 71:
E475: Invalid value for argument cmd: 'C:/Users/opti/.wakatime/wakatime-cli.exe' is not executable