Closed harryghgim closed 2 years ago
Try setting the symlink yourself:
ln -s $(basename ~/.wakatime/*) ~/.wakatime/wakatime-cli
The symlink will be created automatically if you install the CLI via this plugin.
Or alternatively set g:wakatime_CLIPath
.
@harryghgim try adding debug = true
to your ~/.wakatime.cfg
file then start Vim and look for an error message at the bottom.
Every time vim-wakatime loads (on Vim startup) it runs this install script which should create the symlink. If it's failing there should be an error printed with debug = true
.
@harryghgim try adding
debug = true
to your~/.wakatime.cfg
file then start Vim and look for an error message at the bottom.Every time vim-wakatime loads (on Vim startup) it runs this install script which should create the symlink. If it's failing there should be an error printed with
debug = true
.
@alanhamlett After I set debug = true
in cfg file, no earlier than I had set let g:wakatime_CLIPath='/Users/gwanghyeongim/.wakatime/wakatime-cli'
in my vimrc, I see this error message. Maybe my path is wrong somehow?
@kidonng I ran the command, and the result says
ln: /Users/gwanghyeongim/.wakatime/wakatime-cli/wakatime-cli: File exists
So I tried g:wakatime_CLIPath as above, it doesn't seem to help me much either.
I have a feeling that I've missed something too obvious to miss in the end...
That error shown is:
Error: sh: /Users/gwanghyeongim/.wakatime/wakatime-cli: is a directory
Try deleting your ~/.wakatime/
folder then re-launch Vim.
@alanhamlett Thank you so much. My issue is solved now and I'm closing it.
Also, remember to turn off debug mode so your Vim performance won't be impacted:
:WakaTimeDebugDisable
f922f82954cb68fccfd20ad3eacc78fb2559a937 should prevent this from happening in the future.
Having a similar issue, it's trying to run the folder instead of running the binary inside of the folder
You're using the latest vim-wakatime? This change should remove the old directory, so maybe you're not on the latest? https://github.com/wakatime/vim-wakatime/blob/f922f82954cb68fccfd20ad3eacc78fb2559a937/scripts/install_cli.py#L190
If you're using the latest vim-wakatime, try deleting the ~/.wakatime/
folder then restart Vim.
Hi. Thanks for the great vim plugin.
My issue is even if I registered my api key, my wakatime dashboard won't show the sign of vim as registered editor. I ran
:WakaTimeApiKey
and pasted my api key from dashboard, and also made sure that my~/.wakatime.cfg
hasapi_key
value in it.I use wakatime with vscode and sublime text, and no such non-recognition issue happened with them.
And as a related issue I suspect, when I run
:WakaTimeToday
, I see this sign on the bottom:But when I run this file in shell, it seems at least I don't have permission error.
What do you think seems to be the reason of the problem?
For better reproduction of the issue my environments are as follow: