Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @awaescher ,
It's been a while since I started thinking of a way to efficiently find executable paths... First I started a bit of rework of the exe search to add new applications more easily (Git Bash I remember).
I didn't find any reliable solution to search executables in "exotic" directories, so I ended up allowing to do it... in the configuration file !!
Sorry master, to go against your will of a zero config app !! ;)
So , it goes like this :
{
"AutoFetchMode": 0,
"PruneOnFetch": true,
"ExePaths": [{
"ApplicationName": "SourceTree",
"ApplicationFullPath": "C:\Users\######_01.001\AppData\Local\SourceTree\SourceTree.exe"
}, {
"ApplicationName": "GitBash",
"ApplicationFullPath": ""
}, {
"ApplicationName": "WindowsTerminal",
"ApplicationFullPath": ""
}, {
"ApplicationName": "VSCode",
"ApplicationFullPath": ""
}
]
}
=> if no path is provided the good ol' search does the job.