Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Powershell Integrated Console - loops (preview 2.0.2) #1879

Closed
AlexBillon07 opened this issue Apr 15, 2019 · 1 comment
Closed

Powershell Integrated Console - loops (preview 2.0.2) #1879

AlexBillon07 opened this issue Apr 15, 2019 · 1 comment

Comments

@AlexBillon07
Copy link

Issue Type: Bug

The Powershell Integrated Console can't be used.

It loops (cf gif)
Integrated Powershell Console loops

Extension version: 2.0.2
VS Code version: Code 1.33.1 (51b0b28134d51361cf996d2f0a1c698247aeabd8, 2019-04-11T08:27:14.102Z)
OS version: Windows_NT x64 10.0.17134

VS Code version: Code 1.33.1 (51b0b28134d51361cf996d2f0a1c698247aeabd8, 2019-04-11T08:27:14.102Z)
OS version: Windows_NT x64 10.0.17134

System Info
Item Value
CPUs Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 1800)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Memory (System) 15.85GB (9.09GB free)
Process Argv
Screen Reader no
VM 0%
Extensions (10)
Extension Author (truncated) Version
overtype ada 0.2.0
vscode-edifact DAX 0.5.1
xml Dot 2.4.0
gitlens eam 9.6.0
reg ion 0.0.2
powershell-preview ms- 2.0.2
vscode-hexdump sle 1.7.2
poor-mans-t-sql-formatter-vscode Tao 1.6.10
vscode-icons vsc 8.5.0
vsc-jsonsnippets wmo 0.1.4
@AlexBillon07 AlexBillon07 changed the title Powershell Integrated Console - loops Powershell Integrated Console - loops (preview 2.0.2) Apr 15, 2019
@rjmholt
Copy link
Contributor

rjmholt commented Apr 15, 2019

Hi @AlexBillon07, this is likely a known issue in PSReadLine 2.0.0-beta.3 occurring with non-US keyboards (PowerShell/PSReadLine#854 (comment)). We're waiting on the next PSReadLine release for a fix.

It's likely you're experiencing this behaviour now because 2.0.0-preview.3 has PSReadLine turned on by default.

To turn it off, you should be able to set:

"powershell.developer.featureFlags": []

Alternatively you can install PSReadLine 2.0.0-beta.4 from here and try that out.

Deduplicating this issue to #1570.

@rjmholt rjmholt closed this as completed Apr 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants