Replies: 1 comment 8 replies
-
|
I am not quite sure whether I understand your suggestion. With #207 the user can now choose to store their Are you proposing to introduce an environment variable |
Beta Was this translation helpful? Give feedback.
8 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Just started using timewarrior, thanks for the effort.
I noticed having a separate environment variable such as
TIMEWARRIORRCtoseparate the user config from the data files came up several times [1-2].
Although this is addressed somewhat with XDG Base Directory implementation [3],
it doesn't let the user choose a different directory to back-up or sync
the data. Although it is trivial to do
Wouldn't it be better to let user choose whichever place to store data (without
configuration files), via TIMEWARRIORDB (or alternatively with a configuration
option on current default
$XDG_CONFIG_HOME/timewarrior/timewarrior.cfg) ?I yet to see a need to use config file, but wouldn't this allow people to share
the user configuration between instances and only check data to their
back-up/sync solution?
1: #193 (comment), 3rd point
2: #392 (comment)
3: #207
Beta Was this translation helpful? Give feedback.
All reactions