-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WSL / Windows Terminal Integration #14
Labels
Comments
htngr
added a commit
that referenced
this issue
Nov 18, 2024
WSL: windows terminal fragments (solves #14) Updated Logo in MSIX
Implemented in v0.2.4.2 |
htngr
added a commit
that referenced
this issue
Nov 18, 2024
WSL: windows terminal fragments (solves #14) Updated Logo in MSIX
htngr
added a commit
that referenced
this issue
Nov 18, 2024
WSL: windows terminal fragments (solves #14) Updated Logo in MSIX
htngr
added a commit
that referenced
this issue
Nov 18, 2024
WSL: windows terminal fragments (solves #14) Updated Logo in MSIX
htngr
added a commit
that referenced
this issue
Nov 18, 2024
WSL: windows terminal fragments (solves #14) Updated Logo in MSIX
htngr
added a commit
that referenced
this issue
Nov 18, 2024
WSL: windows terminal fragments (solves #14) Updated Logo in MSIX
htngr
added a commit
that referenced
this issue
Nov 18, 2024
WSL: windows terminal fragments (solves #14) Updated Logo in MSIX
htngr
added a commit
that referenced
this issue
Nov 19, 2024
WSL: windows terminal fragments (solves #14) Updated Logo in MSIX
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hiding / Modifying instances in terminal dropdown
Docker Desktops' and Rancher Desktops' distros are hidden via an explicit blacklist
A better way is by adding 'JSON Fragments' to
C:\Users\<user>\AppData\Local\Microsoft\Windows Terminal\Fragments\{app-name}\{file-name}.json
. See rancher-sandbox/rancher-desktop#818 and https://learn.microsoft.com/en-us/windows/terminal/json-fragment-extensionsGoal: Prevent user from launching instance when controller is not running
Possible Solutions:
devenv run <name>
Windows Explorer
WSL uses the distro name (currently
devenv_controller
/devenv_instance_<name>
) when displaying it in explorer / start menu.It would be better to have a more "human friendly" name (e.g. "Devenv ")
Possible Solutions:
The text was updated successfully, but these errors were encountered: