TaskWarrior.load_config() ignores TASKRC environment variable about taskw

[ralphbean]

Hm, since taskw is a library.. I'm not sure it should be responsible for checking environment variables. Should taskwarrior-time-tracking-hook do this instead and pass the value to taskw? @kostajh, do you have an opinion on this?

[coddingtonbear]

Hrm -- I hadn't realized that that environment variable could be used to
point at one's Taskrc file. Given that we already automatically calculate
where one's Taskrc file is in taskw, though, I think it might make the most
sense to do this calculation in taskw. Even better: if it's possible for
us to ask taskwarrior where it will be reading its config from, we could
use that path?

On Tue, Feb 24, 2015 at 12:19 PM, Ralph Bean [email protected]
wrote:

Hm, since taskw is a library.. I'm not sure it should be responsible for
checking environment variables. Should taskwarrior-time-tracking-hook do
this instead and pass the value to taskw? @kostajh
https://github.com/kostajh, do you have an opinion on this?

—
Reply to this email directly or view it on GitHub
#94 (comment).

[khaeru]

This could be as simple as replacing "~/.taskrc" with os.getenv('TASKRC', '~/.taskrc'). Since the former appears in multiple places, perhaps set a global variable near the top of warrior.py:

TASKRC = os.getenv('TASKRC', '~/.taskrc')

…if that's consistent with your coding style.

[ralphbean]

Sure. Want to submit the pull-request @khaeru?