-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable api key prompt if already set in main config #98
Comments
Implemented in v8.6.0 just released. |
Thanks for the fix but it does still prompt with v8.6.0 :/ |
Sorry, probably because of a bug when parsing the config file. Should be fixed now in 8.6.1, can u see if it stops prompting after updating? |
The behaviour has changed. Now, first time it continues prompting and creates a sublime-settings file with my api_key. The next time it stops prompting. I don't want or need to manage several config files for my api key. |
After upgrading to v8.7.0 you can delete your user sublime-settings file and restart Sublime for it to use the common config file without re-creating the sublime-settings file. |
Yes this is now perfect, thanks a lot @alanhamlett ! |
I'm using only the main config file (
.wakatime.cfg
) to set my api_key and some other settings I need for. I don't need to set any overriden value in Wakatime.sublime-settings.However each time I open a new Sublime Text instance, Wakatime prompt me to enter my api key even if it does not prevent it from working as it should. So each time, I hit escape key to skip the prompt but this is kind of annoying.
Could you implement an option to not prompt for an api_key or review the logic behind this ? If this is not intended, I could give you some additionnal informations about my setup.
The text was updated successfully, but these errors were encountered: