Though that may just be a typo on your post. It should be: Set-PSReadLineOption -PredictionSource None Lastly, this command is not valid: Set-PSReadLineOption -Prediction Source None You make PSReadsline settings in those as normal so that you have what you need depending on the shell/console you are in. In VSC PowerShell shells, just this: New-Item –Path $Profile –Type File –ForceĮach profile for PowerShell and VSC are in these locations: # PSCore I've since taken that out so it wouldn't possibly causes issues elsewhere.Ĭreating a PowerShell/pwsh profile is the same as you would in PS/pwsh normally. What I've tried: I noticed I had a $profile file in my Documents so I put the command in there but no change. Outside of VS Code it isn't happening yet.Īnyone having this issue? And how did you solve it? I am am totally clueless when it comes to PowerShell $profiles so all I would do is cause more issues if I started a "trail and error" approach. This is only happening with the VS Code powershell terminal at the moment. At the moment, I am having to issue the Set-PSReadLineOption -Prediction Source None command for each new terminal I bring up in VS Code which is super annoying. is that I do not know how to create a $profile for the VS Code terminal in order to get this disabled. Regardless, it seems like all you have to do is issue the Set-PSReadLineOption -Prediction Source None command to turn it off. A day or two ago, the integrated terminal in VS Code started using Powershell Predictive Intellisense, I think this post might be related to it? ( )
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |