In working around #90, I set the WAKATIME_HOME environment variable to a directory like $HOME/.local/share/wakatime. At the same time, I moved .wakatime.cfg, .wakatime.db, .wakatime.log into this directory.
When I next started Atom, I saw an error message that my API key was not found.
In the Atom settings view, I re-entered my API key.
I noticed the file $HOME/.wakatime.cfg was created, while $WAKATIME_HOME/.wakatime.cfg was not modified.
It seems that when atom-wakatime invokes the wakatime Python core, the latter correctly picks up WAKATIME_HOME, so that the .db and .log files are modified in the correct directory. But the Atom plugin reads and writes the .cfg file in the wrong place. Searching the code in this repo shows that the environment variable is not used.
WAKATIME_HOMEenvironment variable to a directory like$HOME/.local/share/wakatime. At the same time, I moved.wakatime.cfg,.wakatime.db,.wakatime.loginto this directory.$HOME/.wakatime.cfgwas created, while$WAKATIME_HOME/.wakatime.cfgwas not modified.It seems that when atom-wakatime invokes the wakatime Python core, the latter correctly picks up
WAKATIME_HOME, so that the .db and .log files are modified in the correct directory. But the Atom plugin reads and writes the .cfg file in the wrong place. Searching the code in this repo shows that the environment variable is not used.For now I work around this issue with a symlink: