-
Notifications
You must be signed in to change notification settings - Fork 503
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
Deactivation after editor restart #10
Comments
Sorry about that, this is definitely a bug. Does the displayed console output appear each time you restart Sublime? That would indicate that the TabNine package directory is getting overwritten. This would also explain why you needed to reenter the key, since the key is stored in the package directory. |
Weirdly enough, I can not reproduce the bug anymore as of today 😅
I'm guessing the issue will crop up again when you decide to release the next update (my interpretation of the first Sublime Text console output) With kind regards, |
Looks like this is because Package Control deletes all existing files in the directory when it does an update. I'll have to push a TabNine update which moves TabNine config and registration keys to the home directory before updating the Sublime client again. |
First of all: TabNine is awesome, immediately purchased it after using it for 5 minutes.
I have one small problem though: Every time I restart Sublime (3180) I have to enter my license again because TabNine seemingly forgets that it is already activated.
Sublime Console output:
Displayed warning:
With kind regards,
Philip Trauner
The text was updated successfully, but these errors were encountered: