You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For Portable VS Code, Wakatime sets config files in machine's user profile instead of the VS Code data directory. When you open VS Code on a new machine, you have to re-enter the key which is then set in that computer. Currently, the only is to manually move the config files each time you change computer.
In extension.js, this is explicitly specified in line 689 and 193. Expanding these functions to allow for portability would be great.
Currently, my settings to override this was to edit the above function to set config files to the data/extensions-data inside VS Code portable directory but would obviously be overwritten with update
getUserHomeDir(){return'data/extensions-data';}
The text was updated successfully, but these errors were encountered:
For Portable VS Code, Wakatime sets config files in machine's user profile instead of the VS Code data directory. When you open VS Code on a new machine, you have to re-enter the key which is then set in that computer. Currently, the only is to manually move the config files each time you change computer.
In extension.js, this is explicitly specified in line 689 and 193. Expanding these functions to allow for portability would be great.
Currently, my settings to override this was to edit the above function to set config files to the
data/extensions-data
inside VS Code portable directory but would obviously be overwritten with updateThe text was updated successfully, but these errors were encountered: