vscode-powershell: Interactive console does not provide command history in debugger

System Details

Operating system name and version: Windows 7 (64-Bit)
VS Code version: 1.10.2
PowerShell extension version: 0.10.0
Output from $PSVersionTable:

Name                           Value
----                           -----
PSVersion                      5.0.10586.117
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.10586.117
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Issue Description

When executing commands in the integrated terminal, the up and down arrows on the keyboard to browse through command history do not work.

For example:

Execute a command such as Get-Item
When the command is finished, I would expect to be able to press the up arrow on the keyboard and have Get-Item re-appear as the command to run. Instead, the command input remains blank.

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 18
Comments: 48 (6 by maintainers)

Commits related to this issue

Fix command history navigation while debugging This change fixes an issue where the debugger was unable to obtain command history. Resolves PowerShell/vscode-powershell#550 — committed to SeeminglyScience/PowerShellEditorServices by SeeminglyScience 7 years ago

Most upvoted comments

Any update on the issue? As I’m sure everyone agrees this is a pain when debugging.

+11

swt-das on Sep 5, 2017

Really am looking forward to seeing when the update is made to support this, As love vscode but have to resort back to ISE for basic debugging in pwsh 😦

On Mon, 26 Mar 2018 at 10:48, Sharken03 notifications@github.com wrote:

+1 SeeminglyScience has a commit ready since October 2017, but it seems that commit is just the tip of the iceberg. Anyways, would be really good with an ETA, as this issue prevents me from using VS Code with PowerShell.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/PowerShell/vscode-powershell/issues/550#issuecomment-376109446, or mute the thread https://github.com/notifications/unsubscribe-auth/AQYljh79JH47-0AZy6yJSVZM7lL0B038ks5tiLlygaJpZM4MeCh8 .

sdcscripts on Mar 26, 2018

Soon ™ 😉

The PSReadLine PR is almost done.

TylerLeonhardt on Aug 2, 2018

@WaynePlummer Current core work for it is happening in this PR: https://github.com/PowerShell/PowerShellEditorServices/pull/672 But it might take some time afterwards for a release of the vscode-powershell, which is probably going to be of version 2 due to breaking changes (PowerShell versions before 5 will not be supported any more)

bergmeister on Jun 11, 2018

Any update on general availability for this fix yet? I am also in the group who want to drop the ISE but find this issue a show-stopper.

WaynePlummer on Jun 11, 2018

@SeeminglyScience Phew, I’m glad you did not pick one of the many PSUseDeclaredVarsMoreThanAssignments issues that all require a re-write of the rule… Jokes aside, I think your referenced issue is really important because it is a blocker for many people. I had it already in the back of my mind to look at it but you confirmed that it really needs to be investigated and hopefully properly fixed.

bergmeister on Feb 15, 2018

@bergmeister careful now, my price is steep 😉 (PowerShell/PSScriptAnalyzer#850)

SeeminglyScience on Feb 14, 2018

@sba923 Yeah, it’s in the 2.0 which isn’t released yet. There’s a preview build in this comment if you’d like to help test though 🙂

SeeminglyScience on Oct 2, 2018

There’s a preview build available to address this that you can find here: https://github.com/PowerShell/vscode-powershell/issues/535#issuecomment-418944258

Please give it a try – it’s a pretty significant feature, so if you hit any problems please open an issue 😃

rjmholt on Sep 6, 2018

Just updated everything today and saw this feature is still missing. +1 ! 🙏

thomasbtatum on Aug 2, 2018

+1 I would even offer to fix a PSSA issue of your choice in exchange for getting this fixed.

bergmeister on Feb 14, 2018

@SeeminglyScience Thanks for the update. I sympathize with “huge changes”. 😃

yobyot on Jan 23, 2018

Same here: if there’s a way to get a build with that fix in, I’d be delighted to test that!

sba923 on Dec 6, 2017

@SeeminglyScience has a fix for this, we just need to do a bit of verification work before merging it.

daviwil on Nov 28, 2017

Definitely a bug here. I’ll fix it when I overhaul command history in a few days.

daviwil on Mar 15, 2017