Stuck on an issue?

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.

[Suggestion] Windows Terminal profile

See original GitHub issue

For bugs, describe what you’re seeing By default, both WSL distros (Rancher Desktop and Rancher Desktop Data) are listed in Windows Terminal due to the automatic scan of WSL distros. Not sure this is the wanted behavior, however when compared to Docker Desktop, their WSL distros are not listed.

For feature requests, describe what you’d like to add or change Depending on what wants to be achieved by the Dev team, there could be two options for a better user experience:

Hide/Delete both entries from the Windows Terminal (and Preview) profile (Windows path: %USERPROFILE%\AppData\Local\Packages\Microsoft.WindowsTerminal*\LocalState\settings.json)
Only hide/delete the Rancher Desktop Data WSL distro entry as the user can’t/shouldn’t work with it and let the Rancher Desktop available (might be helpful for some debugging)

To Reproduce Steps to reproduce the behaviour:

Have Windows Terminal installed
Have Rancher Desktop installed
Open a new instance of Windows Terminal and click on the profile selector icon

Result

Expected behaviour As stated above, either both or the Rancher Desktop Data should not appear

Screenshots See above

Setup (please complete the following information):

OS: Windows 11
Terminal: Windows Terminal and Windows Terminal Preview
Rancher Desktop version: 0.6.0
Kubernetes version: n/a (or applicable to all)

Thanks a lot for your support.

Issue Analytics

State:
Created 2 years ago
Reactions:2
Comments:5 (2 by maintainers)

Top GitHub Comments

2reactions

zadjii-msftcommented, Jul 7, 2022

the profile GUID for our WSL distributions will be based on the distro name (and therefore effectively constant for us)

Yep! That’s the contract that some other distros are already reliant on, so we’re not about to change that.

1reaction

zadjii-msftcommented, Jul 6, 2022

Hey so maybe we should revisit this discussion. The Terminal totally provides a mechanism by which an application developer can customize profiles the Terminal dynamically generates. You should be able to use fragment extensions to set the hidden property using the updates property. These profiles would still show up in the settings UI for the Terminal, but not in the dropdown. That’s probably an acceptable tradeoff here.

Other discussion: https://github.com/microsoft/terminal/issues/12757