Unless CLI commands and build tool plugins are explicitly configured with a settings file,
they look in the following locations in order of precedence:
$XDG_CONFIG_HOME/pkl/settings.pkl
$APPDATA/pkl/settings.pkl (on Windows only)
~/.config/pkl/settings.pkl
Path pkl/settings.pkl within the $XDG_CONFIG_DIRS search path
(dirs separated by : on Unix, ; on Windows).
/etc/xdg/pkl/settings.pkl
~/.pkl/settings.pkl (legacy location used by Pkl 0.32 and lower)
Returns the relative, descendent directory path between this module and other.
Throws if no such path exists.
For example, if module mod1 has path /dir1/mod1.pkl, and module mod2 has path
/dir1/dir2/dir3/mod2.pkl, then mod1.relativePathTo(mod2) will return
List("dir2", "dir3").
A common use case is to compute the directory path between a template located at the root of a
hierarchy (say rootModule.pkl) and the currently evaluated module (accessible via the
module keyword):
Configuration settings for Pkl itself.