Skip to content

Add env variables CALCURSE_CALDAV_DATA_DIR and CALCURSE_CALDAV_CONFIG_DIR#394

Open
josephmturner wants to merge 1 commit intolfos:pufrom
josephmturner:env-vars-for-caldav-config-and-data
Open

Add env variables CALCURSE_CALDAV_DATA_DIR and CALCURSE_CALDAV_CONFIG_DIR#394
josephmturner wants to merge 1 commit intolfos:pufrom
josephmturner:env-vars-for-caldav-config-and-data

Conversation

@josephmturner
Copy link
Contributor

Allows users to set arbitrary locations for caldav config and data,
without the calcurse-caldav script creating unused caldav directories
inside $XDG_DATA_HOME/calcurse and $XDG_CONFIG_HOME/calcurse.

Addresses #393

Allows users to set arbitrary locations for caldav config and data,
without the calcurse-caldav script creating unused `caldav` directories
inside $XDG_DATA_HOME/calcurse and $XDG_CONFIG_HOME/calcurse.
@josephmturner josephmturner changed the title Add env variables CALCURSE_CALDAV_DATA and CALCURSE_CALDAV_CONFIG Add env variables CALCURSE_CALDAV_DATA_DIR and CALCURSE_CALDAV_CONFIG_DIR Sep 17, 2021
@lfos
Copy link
Owner

lfos commented Oct 16, 2021

Thanks for your contribution, Joseph! If I'm not mistaken, all paths can already be configured using command-line arguments (--config, --hookdir, ...) is there anything that's not covered by them?

You're correct that using them will still lead to standard directories being generated to check_dir() calls. I think we should move the check_dir() calls to a later point in the script, after command line arguments have been parsed. Does that make sense?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants