terminal.integrated.profiles.windows does not work with spaces in names anymore
See original GitHub issueSince one of the recent updates, VSCode does not accept my custom terminal profile anymore (for the Git Bash in this instance). This is what I had configured so far:
"terminal.integrated.defaultProfile.windows": "Git Bash",
"terminal.integrated.profiles.windows": {
"Git Bash": {
"path": "C:\\ProgramData\\scoop\\apps\\git-with-openssh\\current\\bin\\bash.exe"
},
"PowerShell": {
"source": "PowerShell"
}
},
See also https://github.com/microsoft/vscode/issues/123205#issuecomment-834045362
The profile does not work anymore though and within the settings editor VSCode laments “Value is not accepted”:
Has anything changed in the way how you define custom terminals in the recent updates?
Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.71.2
- OS Version: Windows 10 Pro x64, Version 10.0.19044 Build 19044
Steps to Reproduce:
- Create a custom terminal profile under
terminal.integrated.profiles.windows
with thepath
option. - Try to set this as your default profile (or test if you can start a terminal with this profile).
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:17 (6 by maintainers)
Top Results From Across the Web
GitBash not showing up as a terminal option in Visual Studio ...
In double click on Path and add "%GIT_HOME_2%\bin"; Open VS Code, you should now see the bash terminal. { "terminal.integrated.profiles.windows": { "PowerShell" ...
Read more >Terminal Profiles in Visual Studio Code
Visual Studio Code's integrated terminal allows configuring various profiles to make launching various shells easier.
Read more >Cygwin FAQ
My Windows logon name has a space in it, will this cause problems? Most definitely yes! UNIX shells (and thus Cygwin) use the...
Read more >How to set Git Bash as integrated terminal in VSCode in 2021
I'm on Windows 11. I try and works for me if I call the terminal "GitBash" or anyhow but not "Git Bash" with...
Read more >Command-line API | Node.js v19.3.0 Documentation
To view this documentation as a manual page in a terminal, run man node . ... If --cpu-prof-name is not specified, the generated...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, because if I change the name from
"Git Bash"
to"GitBash"
it works.Thanks for pointing that out. we had an issue at one point where the exact name of “Git Bash” was the problem and I was confusing that w this. I can reproduce the issue you describe though