You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
This feature request is a workaround related to windows bug (unconfirmed?) when setting ComSpec to powershell
Steps to reproduce the issue (not related to WezTerm):
Set ComSpec environment variable to powershell, like C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Create a .bat file with contents pause
Try to run the .bat file by double clicking on it, you'll see that roughly 10 powershell instances are spawned every second, causing the system to eventually run out of memory. Delete the bat file to kill all of the powershell instances before this happens
Not sure what causes this behaviour but it is untenable to change ComSpec at this time.
Describe the solution you'd like
Provide a way to specify the default shell without the use of ComSpec, maybe something like WEZTERM_DEFAULT_SHELL as an environment variable.
Everywhere online seems to suggest that you shouldn't alter the value of ComSpec since a lot of programs will assume it points to cmd.
Describe alternatives you've considered
A quick workaround is to call powershell in CMD every time i open wezterm, but that is annoying.
Additional context
This is the only other report related to the same issue I've found
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.
Is your feature request related to a problem? Please describe.
This feature request is a workaround related to windows bug (unconfirmed?) when setting ComSpec to powershell
Steps to reproduce the issue (not related to WezTerm):
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
.bat
file with contentspause
.bat
file by double clicking on it, you'll see that roughly 10 powershell instances are spawned every second, causing the system to eventually run out of memory. Delete the bat file to kill all of the powershell instances before this happensNot sure what causes this behaviour but it is untenable to change ComSpec at this time.
Describe the solution you'd like
Provide a way to specify the default shell without the use of ComSpec, maybe something like WEZTERM_DEFAULT_SHELL as an environment variable.
Everywhere online seems to suggest that you shouldn't alter the value of ComSpec since a lot of programs will assume it points to cmd.
Describe alternatives you've considered
A quick workaround is to call
powershell
in CMD every time i open wezterm, but that is annoying.Additional context
This is the only other report related to the same issue I've found
sbt/sbt#6643
The text was updated successfully, but these errors were encountered: