Accept configuration path as argument

[asymmetric]

I’m packaging acts for the nix package manager, and it would help if the paths to the configuration file weren’t hardcoded.

Are you open to this change? If so, I could probably come up with a PR.

[alexjurkiewicz]

That sounds reasonable. The behaviour if you pass this argument would be to source only the specified file, and to fail if the file is unreadable. A pull request would be welcome!

…

On Mon., 21 Jan. 2019, 19:45 Lorenzo, ***@***.***> wrote: I’m packaging acts for the nix package manager, and it would help if the paths to the configuration file weren’t hardcoded. Are you open to this change? If so, I could probably come up with a PR. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#27>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAXKdZHP_oBzq0pBd_G9IDHJ_6a7lOSpks5vFX41gaJpZM4aKWHy> .

[asymmetric]

I would also then remove the implicit laoding of a file from the current directory, since people will be able to just specify the file explicitly. Cool?

[alexjurkiewicz]

Yes, I would be happy to see the end of that!

…

On Tue., 22 Jan. 2019, 00:22 Lorenzo, ***@***.***> wrote: I would also then remove the implicit laoding of a file from the current directory, since people will be able to just specify the file explicitly. Cool? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#27 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAXKdVRG0VVn6GSmQbGtieayYnCx7OXdks5vFb8MgaJpZM4aKWHy> .