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

On Windows 11 History not working #5525

Open
StandardNerd opened this issue Jun 7, 2024 · 1 comment
Open

On Windows 11 History not working #5525

StandardNerd opened this issue Jun 7, 2024 · 1 comment
Labels
bug Something isn't working keyboard Keyboard mapping/handling Windows Issue applies to Microsoft Windows

Comments

@StandardNerd
Copy link

What Operating System(s) are you seeing this problem on?

Windows

Which Wayland compositor or X11 Window manager(s) are you using?

On Linux Wezterm's history by using arrow key "up" is working fine. But on Windows 11 the history is not working:

  1. Start Wezterm
  2. press arrow key "up"
  3. nothing happens

Expected behaviour:

the last command should appear.

WezTerm version

20240203-110809-5046fc22

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

Yes, and I updated the version box above to show the version of the nightly that I tried

Describe the bug

On Linux Wezterm's history by using arrow key "up" is working fine. But on Windows 11 the history is not working for past session. Only for the current session. If I close Wezterm and start it again, the history is cleared. How to make the history persistent so that it's available in tomorrow's session (default behaviour on most terminals like Git Bash even on Windows)?

To Reproduce

  1. Start Wezterm
  2. press arrow key "up"
  3. nothing happens

Configuration

nothing special, just some configurations for fonts.

Expected Behavior

the last command should appear.

Logs

No response

Anything else?

No response

@StandardNerd StandardNerd added the bug Something isn't working label Jun 7, 2024
@wez wez added Windows Issue applies to Microsoft Windows keyboard Keyboard mapping/handling labels Jul 15, 2024
@HeyItsGilbert
Copy link

Which shell are you using? cmd won't do this. It barely does anything. You may want to set your default config.default_prog to PowerShell.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working keyboard Keyboard mapping/handling Windows Issue applies to Microsoft Windows
Projects
None yet
Development

No branches or pull requests

3 participants