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

Home/End/Del don't work with zsh under Git for Windows #16762

Closed
jathek opened this issue Feb 25, 2024 · 3 comments
Closed

Home/End/Del don't work with zsh under Git for Windows #16762

jathek opened this issue Feb 25, 2024 · 3 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@jathek
Copy link

jathek commented Feb 25, 2024

Windows Terminal version

1.20.10303.0

Windows build number

10.0.19045.3930

Other Software

Git for Windows 2.43.0 winget install --id Git.Git -e --source winget
zsh 5.9-2: https://packages.msys2.org/package/zsh?repo=msys&variant=x86_64

Steps to reproduce

  1. Install Git for Windows
  2. Install zsh by extracting the .zst to %ProgramFiles%\Git
  3. Try to use Home/End/Del keys in a zsh session in Git Bash

Expected Behavior

The keys to work

Actual Behavior

Nothing happens. Several threads around the internet mention trying to use "cat" to identify the escape character for Home or End, but Windows Terminal doesn't print anything when doing that.

It looks like #8179 was a similar issue, with a couple of people towards the end of the issue mentioning that they have similar issues. It doesn't look like the issue was ever resolved for them though.

@jathek jathek added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Feb 25, 2024
@carlos-zamora
Copy link
Member

Thanks for filing. This should be fixed in 1.20.10532.0 via PR #16675. We're going to mark this as a /dup of #16672

Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot 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 labels Feb 28, 2024
@jathek
Copy link
Author

jathek commented Feb 28, 2024

Thanks for filing. This should be fixed in 1.20.10532.0 via PR #16675. We're going to mark this as a /dup of #16672

Sounds good. I ended up installing oh-my-zsh just to finish configuring things, and all the keys I mentioned started working again. I assume it's binding the keys somewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants