VSCode PowerShell Preview PSES no longer shows history from previous F8/F5 command in buffer
See original GitHub issuePrerequisites
- I have written a descriptive issue title.
- I have searched all issues to ensure it has not already been reported.
- I have read the troubleshooting guide.
- I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
- I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
Summary
The current behavior of the PowerShell Extension is to show the history in the Terminal after using F5 or F8
- This is available with the up arrow to re-execute the previous command; however this is missing in the current preview.
Typo on my video: “Up arrow does not show history”
There are also some artifacts and clearing of the screen when executing the second command, however I didn’t open this issue for that.
https://user-images.githubusercontent.com/3605266/141012338-b3f9dd95-575d-4dc5-a06f-bc7d8d98a37e.mp4
issue starts at 30 seconds onwards.
PowerShell Version
Name Value
---- -----
PSVersion 7.2.0-preview.10
PSEdition Core
GitCommitId 7.2.0-preview.10
OS Microsoft Windows 10.0.22499
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Visual Studio Code Version
1.62.0
b3318bc0524af3d74034b8bb8a64df0ccf35549a
x64
Extension Version
ms-vscode.powershell@2021.10.2 # disabled
ms-vscode.powershell-preview@2021.11.0
Steps to Reproduce
run a command from the script pane with F8 watch it execute Go to the terminal and press the up arrow, the previous command is not in the buffer It is shown in the history
Visuals
video is above, you can skip to 30 seconds.
Logs
No response
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:13 (7 by maintainers)
Top Results From Across the Web
PowerShell editing with Visual Studio Code
command from the Command Palette (Ctrl+Shift+P) or by changing the default settings editor with the "workbench. settings. editor" setting.
Read more >How to replicate the ISE experience in Visual Studio Code
The easiest way to replicate the ISE experience in Visual Studio Code is by turning on "ISE Mode". To do this, open the...
Read more >How can I clear the terminal in Visual Studio Code?
Every time I use Maven, the output of the terminal is attached to the previous build, which is confusing me. How do I...
Read more >VS Code tips — The Terminal scrollback setting - YouTube
Today's VS Code setting: Terminal scrollbackAdjust how much history the integrated terminal keeps in its buffer.Useful when running commands ...
Read more >VS code terminal disable previous commands output
The bug seems to be that the cls command clears the screen, but does not clear the scrollback buffer of the terminal, where...
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
It’s shown in
Get-History
but not PSReadLine history. BasicallyPSConsoleReadLine.AddToHistory(string)
needs to be called somewhere.I agree with @ruudhanegraaf, this was one of the features I loved from vscode vs ise. A lot of times I run my initial command in the editor and then modify it in the console after by pressing up. I was hoping there can be at least an optional setting for this.