Skip to content
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

Closed
PhilipTrauner opened this issue Nov 13, 2018 · 3 comments
Closed

Deactivation after editor restart #10

PhilipTrauner opened this issue Nov 13, 2018 · 3 comments

Comments

@PhilipTrauner
Copy link

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:

reloading plugin TabNine.TabNine
reloading settings Packages/TabNine/TabNine.sublime-settings
TabNine: starting version 0.4.7
Exception while interacting with TabNine subprocess: [Errno 32] Broken pipe
TabNine: starting version 0.11.2

Displayed warning:

image

With kind regards,
Philip Trauner

@zxqfl
Copy link
Contributor

zxqfl commented Nov 13, 2018

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.

@PhilipTrauner
Copy link
Author

Weirdly enough, I can not reproduce the bug anymore as of today 😅

reloading plugin TabNine.TabNine
plugins loaded
TabNine: starting version 0.11.2

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,
Philip Trauner

@zxqfl
Copy link
Contributor

zxqfl commented Nov 17, 2018

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.

@zxqfl zxqfl closed this as completed in bca744f Nov 21, 2018
zxqfl added a commit that referenced this issue Nov 21, 2018
Closes #5
Closes #7
Closes #8
Closes #10
Closes #11
Closes #14
Closes #15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants