Closed cderv closed 4 years ago
The path is hardcoded at the moment, but it can be changed in the configuration. I'm starting to think I should look for both though, add profiles from both configuration files in the catalog, and open them in the expected version.
I'm starting to think I should look for both though, add profiles from both configuration files in the catalog, and open them in the expected version.
Yes this could be a good idea ! It would allow to work without modifying configuration.
The path is hardcoded at the moment, but it can be changed in the configuration. I
Thanks I had not check before opening the issue ! 😅
There's a new release which should support multiple installations. Could you give it a try and see if it works as you would expect?
Note that the configuration format has slightly changed, so if you defined a custom item prefix you'll have to move it to the section matching the installation you want it to apply to.
Yes this now install and works as expected thank you !
Glad to read that!
Maybe it is also related to #4 as I am using the Terminal Preview
I got this at installation
This is because the setting file is in
Note the Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe while the extension is looking in Microsoft.WindowsTerminal_8wekyb3d8bbwe
Let's note that wt.exe is existing and is for the preview version..
How do you determine the setting folder ?