Closed tosie closed 2 years ago
@tosie, we can call it a bug, I haven't predicted the case of included files being symlinks to other files.
Anyway, I've fixed it (I believe) in the latest beta build, which I've just uploaded. It's version 1.7.5b1 (build 119) and you can download it directly here, but you can also update your current copy to it automatically, just select Beta update channel in the preferences, like in the picture below:
This version should handle included symlinks correctly, but just be aware that, when reporting included files, GitFinder will not report symlinks defined in config file(s), it will report symlinked targets instead, like for example in the pictures below:
You probably realise selecting included files is necessary to include them in GitFinder sandbox environment (GitFinder is fully sandboxed application).
Please try this beta build and let me know if it solves your problem.
@tosie, any luck with the latest beta?
I am so sorry ... just today I came back to my mac and what can I say: It works fine. Thank you very much for the quick update!
I am using the include directive in my .gitconfig to have different sets of config options for different types of machines like this:
Some of the included files are symlinked like this:
When starting GitFinder, this message is shown:
The includes settings look like this:
Now when trying to match a file by selecting the symlink -- which is the only correct file path that matches the include directive -- this error message is shown:
Is there any way to use symlinked .gitconfig-includes?