Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow to set custom installation paths for supported diff tools
See original GitHub issueIs the feature request related to a problem
I have a custom installation folder for both VS Code and Visual studio. The search paths for these diff tools don’t match with the ones hard-coded inside DiffEngine.
Describe the solution
One should be able to set a custom path for diff tools, for example with the help of environment variables.
For example: DiffEngine_<DiffToolName>_Path = D:\My\Folder\
Describe alternatives considered
As alternative, consider reading a configuration file in the home directory of the user or in the project folder.
Additional context
If necessary ask me.
Issue Analytics
- State:
- Created 9 months ago
- Comments:14 (14 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
if u want to do a pull request for that, i am happy to consider it
I want to stress the fact that forcing a parsing of the system PATH it’s not a very good practice in general. One should be able to configure exact specific paths to executables of their diff programs. This avoids mistakes and confusion on which executable the engine is running in case of multiple installation of the same program and some other edge cases…