Giovanni Bassi

If we use the above script (which expands environment variables) I believe we could close #141. What do you think?

> * What if we use `githooks.runnerCustom` which gets checked first in the `run-wrapper.sh`, which is a way of customizing having a custom `run-wrapper.sh`. Still dont know why you need...

> * Then also store by default `$HOME/.githooks` as prefix to all paths in the Git config not the expanded version if [feat: Add expansion of env. variables in Git...

> But your use case: Have a correct `gitconfig` file in your dotfiles repo (yes with `$HOME`) and deploying it, and then installing Githooks (fresh), should work as it substitutes...

> Are you fine with having `githooks.installDir = "$HOME/..."` and the other variables `githooks.runner` and `githooks.dialog` unset in you rdotfiles? Then the installer just changes these values to full paths...

I just added to the issue, `.githooks.manualTemplateDir` also need to work with environment variables.

With the new 3.0 release I see a new property which needs to support environment variables: `pathForUseCoreHooksPath`.

What you have to do is build a project context and work from there. It is quite common, and most tools that need to work with the project data need...

Sure, send a PR.

@christian-bromann docs still mention it as experimental.