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.

Sign up for GitHub

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

Jump to bottom

Powershell doesn't respect clear history #4461

Closed
jrd-lewis opened this issue Feb 4, 2020 · 2 comments
Closed

Powershell doesn't respect clear history #4461

jrd-lewis opened this issue Feb 4, 2020 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@jrd-lewis
Copy link

Environment

Windows build number: 10.0.18363.0
Windows Terminal version: 0.8.10.10261.0

Steps to reproduce

  • Open a PowerShell tab
  • Enter any command
  • Type [Microsoft.PowerShell.PSConsoleReadLine]::ClearHistory()
  • Open new PowerShell tab
  • Press the up arrow key on the keyboard

Expected behavior

PowerShell should not have any commands in the history, accessed via the up arrow key.

Actual behavior

PowerShell seems to forget the history in the current tab; but when you open a new tab and press the up arrow, it still has the PowerShell history.
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Feb 4, 2020
@DHowett-MSFT
Copy link
Contributor

/dup #3126

@ghost
Copy link

ghost commented Feb 4, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Feb 4, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Feb 4, 2020
@jrd-lewis jrd-lewis mentioned this issue May 14, 2020
Closed
@jrd-lewis jrd-lewis mentioned this issue Jul 6, 2022
Merged
7 tasks
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DHowett-MSFT @jrd-lewis