Closed albertosantini closed 9 years ago
Yes, that's the convention for Sublime Text so users are used to looking for a [Plugin].sublime-settings file for any plugin's configs. The ~/.wakatime.cfg is just for the common wakatime cli.
Are you wanting your WakaTime.sublime-settings file on GitHub for backing up or sharing? If just for sharing, why not do this:
WakaTime.sublime-settings
WakaTime.sublime-settings
to git and push to GitHubgit update-index --assume-unchanged WakaTime.sublime-settings
WakaTime.sublime-settings
git should ignore changes in your WakaTime.sublime-settings
from now on.
Nice suggestion. Thanks.
Minor suggestion. I would change the text of the FAQ (in bold the changes) because "or" is a bit confusing:
Make sure to update your api key in $HOME/.wakatime.cfg
(for wakatime cli) or WakaTime.sublime-settings
(for plugin) with your newly generated api key.
Ok thanks!
After reading FAQ (see #42) and adding the api key in
.wakatime.cfg
, when SublimeText is started, it prompts to enter the wakatime.com api key, the input field is filled with the api key.Is this behavior expected? Is it mandatory to create the settings
WakaTime.sublime-settings
?