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
$ ls -a ~ | grep wakatime
.wakatime
.wakatime-internal.cfg
.wakatime.bdb
.wakatime.cfg
.wakatime.data
.wakatime.log
So after some digging you find $WAKATIME_HOME, which is great except it is not obvious how to set environment variable in Windows and especially macOS, which keeps the environment in some obscure location.
Describe the solution you'd like to see
$WAKATIME_HOME should have a more sensible default that doesn't clutter user's home directory, like $XDG_CONFIG_HOME/wakatime (where $XDG_CONFIG_HOME defaults to $HOME/.config if not set), or $HOME/.wakatime where the CLI is already stored.
Describe alternatives you've considered
Ask everyone to set $WAKATIME_HOME 🤷
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Convenient, right? Until you come up with the same question as many others have:
So after some digging you find
$WAKATIME_HOME
, which is great except it is not obvious how to set environment variable in Windows and especially macOS, which keeps the environment in some obscure location.Describe the solution you'd like to see
$WAKATIME_HOME
should have a more sensible default that doesn't clutter user's home directory, like$XDG_CONFIG_HOME/wakatime
(where$XDG_CONFIG_HOME
defaults to$HOME/.config
if not set), or$HOME/.wakatime
where the CLI is already stored.Describe alternatives you've considered
Ask everyone to set
$WAKATIME_HOME
🤷Additional context
The text was updated successfully, but these errors were encountered: