Default Integrated Terminal Shell sometimes not used on launch for remote workspaces #128763
Comments
|
(Experimental duplicate detection) |
|
Not a duplicate of suggestion as I am not splitting the terminal window. My issue pertains to initially created terminal window upon VS Code launch. |
|
|
|
Have same problem. If VSC exits with at least one Integrated Terminal running, it will re-run a single Integrated Termianl on startup. However it will not re-run any of the profiles that were previously running, nor the current default profile - it will just re-run the out-of-the-box default (in my case, vanilla bash to WSL2). Would be good to at least re-run the current default profile (best), or else have an option to not remember that an Integrated Terminal was running previously (OK). |
|
I believe this is already fixed, can you see if you can reproduce in the Insiders build? |
|
Hi Megan,
Yes, can reproduce, still happens on the Insiders build (1.59.0-insider).
David
…On Wed, 28 Jul 2021, at 2:03 AM, Megan Rogge wrote:
I believe this is already fixed, can you see if you can reproduce in the Insiders build <https://code.visualstudio.com/insiders>?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#128763 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKJIVXYZHTKQQFFEF2BQLBLTZ3KGVANCNFSM5ANYZ7RQ>.
|
|
Hi, I am experiencing the same problem as reported above with Visual - see attached reproduction of the issue in a little movie. Visual.Code.Terminal.Issue.mp4 |
|
i can't repro tihis. pls provide me with your settings @amalaussena |
|
#129971
Anais Malaussena
***@***.******@***.***>
www.epo.org<http://www.epo.org>
Please consider the environment before printing this email.
From: Megan Rogge ***@***.***>
Sent: 02 August 2021 17:12
To: microsoft/vscode ***@***.***>
Cc: Anais Malaussena ***@***.***>; Mention ***@***.***>
Subject: Re: [microsoft/vscode] Default Integrated Terminal Shell (#128763)
i can't repro tihis. pls provide me with your settings @amalaussena<https://github.com/amalaussena>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#128763 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVB4BGWEAFY6ABHBETD525DT22YVZANCNFSM5ANYZ7RQ>.
|
|
can anyone provide me with their user settings? to do this, |
|
I'm not sure how @amalaussena 's video shows the problem? The problem happens when VSC launches (as the OP said), and that is not in the video. Anyway, my settings are below. I've pasted both User and Workspace as I have settings across both. And the terminal settings are in Workspace at the bottom. Hope this helps! User{ Workspace{ |
|
Hi @aupsloptp thanks for your help in this issue. The issue is that even if bash is set as the default terminal, when opening a new terminal VSC always selects cmd and there is no way to change this. This is the behaviour I tried to show in the video. |
|
I have the similar issue after last update: |
|
As mentioned above - issue can be reproduced in latest Insiders build // "terminal.integrated.shell.windows": "C:\\Program Files\\Git\\bin\\bash.exe",
// "terminal.integrated.shellArgs.windows": ["--login", "-i"],
"terminal.integrated.profiles.windows": {
"PowerShell": {
"source": "PowerShell",
"icon": "terminal-powershell"
},
"Command Prompt": {
"path": [
"${env:windir}\\Sysnative\\cmd.exe",
"${env:windir}\\System32\\cmd.exe"
],
"args": [],
"icon": "terminal-cmd"
},
"Git Bash": {
"source": "Git Bash"
}
},
"terminal.integrated.defaultProfile.windows": "Git Bash",
Default terminal correctly marked in Launch profile dropdown Version: 1.60.0-insider (user setup) |
|
in insider's today, there's an issue with the default profile that will be fixed tomorrow - #130268 I just re-read the OP description and think I now understand your problem. Commenting out the other shells won't work. You need to set them to null in your settings in order to remove them from appearing in the dropdown. Please let me know if you are still seeing issues with this in tomorrow's insider's. |
|
@meganrogge Can you please comment on the OP's post:
The key words are "upon VS Code launch". It does appear that somehow we are now looking at a different problem (the PowerShell one). Note that the OP also says "the automatically created integrated shell window". The problem as the OP described (and me) ONLY happens on VSC launch, not as @IllusionMH described. See my original post, I am pretty sure that aligns with the OP. If the general consensus is not, then no problem, I will raise a new issue. Maybe the title of this issue is the misleading bit? Maybe it should have been "Default Integrated Terminal Shell Upon Launch". |
|
meganrogge
changed the title
meganrogge
added
terminal-profiles
bug
|
Can't repro, but seems like some people are seeing this still |
|
For me when (re)launching VSCode with terminal opened the powerShell shows, but if terminal is closed and then manually opened (ctrl + ç) then my default profile (git bash) is shown |
This can be reproduced on my machine with the following settings: Opening a Project directory from Explorer with VS Code launches Code with a PowerShell terminal window. After deleting the PowerShell window (with delete button), and relaunching terminal Ctrl-` it reverts to Selected Git bash profile. A temporary solution until this is fixed is to prevent the PowerShell profile from appearing in the menu by setting its source to "null" |
It doesn't work setting "null" , it is even an invalid value |
|
Only workaround i found (after hours of thread reading and trying to edit settings.json with no success in getting it to stick) was downgrading to 1.59 where it functions perfectly, i didn't even know auto upgrades were a thing for vscode, all i know is i was working on a project just fine then later in the afternoon reopened vscode and this extremely annoying thing was happening. I am scared to death of auto updates and to update vscode period because it does this on the stable build as well, directly from the site. I have since now disabled auto updates. I am a coding student who is just now graduating school so my familiarity with vscode is very limited. I am on windows 10 64 bit |
|
Having this issue after an auto update as well. Having issues with Windows 10 64 bit ignoring my default profile and opening up powershell. |
Reinstall version 1.59 over the top of 1.60 and disable auto updates, that is what i have resorted to as a work around, just go into your settings and type update and disable them, except the extensions. I didn't lose anything by downgrading this way thank god, it was absolutely driving me nuts though not being able to set it to default and having powershell open for everything regardless of which one i chose. |
|
I can report that I'm having the same issue. Rolled back to |
|
I can confirm, using 1.60.0 still opens using powershell upon launch. |
|
Confirming the issue still happens when I tried to run even when I tried to do the following in |
|
Per my issue concerning bash shells (#132312), I confirm this is still happening on the August stable release too. |
|
How to downgrade when using scoop ScoopInstaller/Scoop#4345 (comment) |
|
I'm experiencing this annoying issue after updating to 1.60.0 stable release. I mean when I close VS Code and open it again, at startup it opens And my "terminal.integrated.profiles.windows": {
"PowerShell": {
"source": "PowerShell",
"icon": "terminal-powershell"
},
"Command Prompt": {
"path": [
"${env:windir}\\Sysnative\\cmd.exe",
"${env:windir}\\System32\\cmd.exe"
],
"args": [],
"icon": "terminal-cmd"
},
"Git Bash": {
"source": "Git Bash",
"icon": "terminal-bash"
},
},
"terminal.integrated.defaultProfile.windows": "Git Bash", |
|
can we get an easy update until this is fixed? update to not open an integrated terminal on start? |
|
|
|
Should be already fixed in latest Insiders build @jmanthony3 could you check Insiders build to see if it still preproduces for you? |
Fixed here |
Yep, fixed here too |
|
/duplicate #132150 |
and others
Issue Type: Bug
Opening VS Code automatically creates an integrated shell window, which is what I want. However, despite setting the "cmd.exe" shell as the default and commenting out the other options that only the "Command Prompt" shell is listed to create another terminal windows, the automatically created integrated shell window opens with PowerShell. I don't want PowerShell. If I add another terminal window, then that new window uses the "Command Prompt" shell.
VS Code version: Code 1.58.1 (2aeda6b, 2021-07-13T06:58:28.115Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No
System Info
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: