Closed TheElegantCoding closed 1 year ago
It is an expected behaviour. VS Code expects a path to a shell not to a terminal emulator. For example cmd.exe
, powershell.exe
, pwsh.exe
, bash.exe
or bash
, zsh
, fish
etc. Wezterm on the other hand is a standalone alternative to VS Code's integrated terminal (which is based on xtermjs) and is not supposed to run inside it.
yeah you are right, thanks
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
What Operating System(s) are you seeing this problem on?
Windows
Which Wayland compositor or X11 Window manager(s) are you using?
No response
WezTerm version
wezterm 20230408-112425-69ae8472
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
Maybe this issue is not related to wezterm, when I put windows in vscode the wezterm as a terminal it doesn't open correctly at the bottom of vscode, still, i want to make sure if i am running everything correctly
When i launch the wezterm in vscode this happens, it doesn't fit in the terminal section of vscode it runs the terminal out of vscode, like executing the .exe
To Reproduce
No response
Configuration
Expected Behavior
No response
Logs
No response
Anything else?
No response