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

F7 command history stopped working. #7369

Closed
FDFessler opened this issue Aug 21, 2020 · 4 comments
Closed

F7 command history stopped working. #7369

FDFessler opened this issue Aug 21, 2020 · 4 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@FDFessler
Copy link

Environment

Windows build number: Microsoft Windows [Version 10.0.19041.450]
Windows Terminal version (if applicable): Version: 1.2.2234.0

Any other software?

Steps to reproduce

  1. Launch Windows Terminal Preview
  2. Launch Command Prompt from WT
  3. Enter a couple of commands (dir, ping, etc.)
  4. Press F7 key to bring up command history

Expected behavior

Normally the History Window would appear like it does in the regular command prompt.
I know it was working in the non-preview version. I thought it might be my PC at work so I installed WT Preview (same version as listed above) and that has the same issue (no command history comes up). I am fairly confident this was working in a previous version of WT Preview that I had.

Actual behavior

Nothing. No command history window pops up. :-(
@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 Aug 21, 2020
@DHowett
Copy link
Member

DHowett commented Aug 21, 2020

/dup #7297, fix out soon 😄

@ghost
Copy link

ghost commented Aug 21, 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 Aug 21, 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 Aug 21, 2020
@FDFessler
Copy link
Author

Great to hear it will be worked on, sorry I didn't find the other issue in my search :-( !!

@DHowett
Copy link
Member

DHowett commented Aug 22, 2020

You don’t need to apologize! 😄

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 @FDFessler