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
After updating to 5264d22 after resolving #1225, I tried a brew bundle dump and it opened a VScode window just before the process exited. It opened to the file \Ubuntu\mnt\c\Program Files\Microsoft VS Code\resources\app\out\cli.js as a new, unsaved file. The path is sensible: this Homebrew installation is in WSL. However, I'd not expect VScode to open another window, esp. when I already have one open, and open in the WSL scope at that.
I'm not sure what's happening. It's not very annoying to me because I don't use brew bundle dump regularly.
One thing I tried is what Bundle::VscodeExtensionDumper#extensions does: code --list-extensions. Running this in a WSL terminal did not open another VScode window.
The text was updated successfully, but these errors were encountered:
After updating to 5264d22 after resolving #1225, I tried a
brew bundle dump
and it opened a VScode window just before the process exited. It opened to the file\Ubuntu\mnt\c\Program Files\Microsoft VS Code\resources\app\out\cli.js
as a new, unsaved file. The path is sensible: this Homebrew installation is in WSL. However, I'd not expect VScode to open another window, esp. when I already have one open, and open in the WSL scope at that.I'm not sure what's happening. It's not very annoying to me because I don't use
brew bundle dump
regularly.One thing I tried is what
Bundle::VscodeExtensionDumper#extensions
does:code --list-extensions
. Running this in a WSL terminal did not open another VScode window.The text was updated successfully, but these errors were encountered: