-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Inklecate path configuration for multiple developers #35
Comments
If Are there any viable workarounds? |
Hey @BenjaminLawson, sorry I did not answer earlier. |
We have the same issue on our project, and since we have developers using Mac and Windows, this solution helps a little but does not solve all problems (since the inklecate binary is not the same for windows and mac) I think i'll fork the plugin and have two distinct inklecate path properties : "inklecate-mac" and "inklecate-windows", both relative to |
Humpf, I didn’t think about that either (seems like I don’t think much these days).
If you want to open a PR with what you’re suggesting I’m open to merging it. I feels it is a decent temporary solution while I (or more probably someone else) come up with a really good way of handling this.
|
As of dde8c31, the setting can be overridden from a file that can be excluded from VCS. This will be available in |
Currently, the
inklecate
settings path is shared by all developers for the same project. This is not viable because different developers have different paths to theirinklecate
binary.Inkgd solves this by writing the binary paths to a config file that can be kept out of version control: https://github.com/ephread/inkgd#editor
The text was updated successfully, but these errors were encountered: