Leverage User Settings

[wakatime]

Leverage User Settings

[alanhamlett]

That's doable, we could even only prompt for specific setting keys that are found in both ~/.wakatime.cfg and VS Code Settings, and only when those setting's have different values.

[alanhamlett]

The reason we use ~/.wakatime.cfg is because many people have multiple editors and this way all the editors share the same config file. If there's a way to keep the user settings in sync with a local file, then we could use both.

[mpearon]

Ah, that makes sense.
not sure how efficient this would be, because it would increase the initialization time, but initialization could look to settings first, then to the cfg.

• If the CFG doesn’t exist, and the Setiings don’t exist, create both.
• If the CFG doesn’t exist, and the Settings do, create the CFG based on the Settings.
• If the CFG exists and the Settings don’t, create the settings based on the CFG.
• If both exist, but differ, prompt the user in the UI, updating both.

[mpearon]

Any more thoughts on this one, @alanhamlett ?

[mpearon]

@alanhamlett - Awesome! It seems like I'm asking a lot of you lately. :)

[gandarez]

What's the status of this issue @alanhamlett?

[vilicvane]

@alanhamlett Currently we have shared remote workspaces (for Remote SSH to connect), thus it is necessary for us to have WakaTime reading the settings using the VSCode settings mechanism. Also we need to have the option to disable .wakatime.cfg so that it won't prompt when missing.

[gandarez]

is that a feature already inmplemented/needed @alanhamlett?

[alanhamlett]

is that a feature already inmplemented/needed @alanhamlett?

If we pass --key to wakatime-cli does it complain about missing ~/.wakatime.cfg or does it work without the config file?

[gandarez]

If we pass --key to wakatime-cli does it complain about missing ~/.wakatime.cfg or does it work without the config file?

It won't complain about missing config file unless you provide key flag.