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
{{ message }}
This repository has been archived by the owner on Sep 24, 2020. It is now read-only.
I'm currently reorganizing my dotfiles in a way more compliant to the XDG Base Directory Specification to make my home directory less cluttered. Many softwares including latexmk follow this specification and I'd be glad if DiCy joins the party.
In that case, $XDG_CONFIG_HOME/dicy/dicy.yaml will be read instead of ~/.dicy.yaml (file name might be change at this point as the dicy subdirectory explicitly describes the YAML file is about DiCy). If $XDG_CONFIG_HOME is unset or empty, it should be replaced with $HOME/.config. The YAML file in user's home directory can still be used and whether or not to keep backward-compatibility is entirely up to you of course.
The text was updated successfully, but these errors were encountered:
I'm currently reorganizing my dotfiles in a way more compliant to the XDG Base Directory Specification to make my home directory less cluttered. Many softwares including latexmk follow this specification and I'd be glad if DiCy joins the party.
In that case,
$XDG_CONFIG_HOME/dicy/dicy.yaml
will be read instead of~/.dicy.yaml
(file name might be change at this point as thedicy
subdirectory explicitly describes the YAML file is about DiCy). If$XDG_CONFIG_HOME
is unset or empty, it should be replaced with$HOME/.config
. The YAML file in user's home directory can still be used and whether or not to keep backward-compatibility is entirely up to you of course.The text was updated successfully, but these errors were encountered: