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

CMD+. to macOS via VNC does not act as expected #5465

Open
tamlok opened this issue May 24, 2024 · 0 comments
Open

CMD+. to macOS via VNC does not act as expected #5465

tamlok opened this issue May 24, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@tamlok
Copy link

tamlok commented May 24, 2024

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

macOS

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

No response

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

I am working on Windows and use Acronis to connect to a MacOS machine via VNC.

When I press CMD+., it acts as Ctrl+C on the default terminal of MacOS to abort current command.

However, when using WezTerm, it only prints 6;1u on the screen.

And the leader key is set to Ctrl+A of my WezTerm config. However when I press CMD+A, it prints 7;1u.

I don't know if it's WezTerm's issue or the VNC client's issue. What does these chars mean here?

To Reproduce

  1. VNC to a MacOS from Windows
  2. Press CMD+. in WezTerm

Configuration

no config

Expected Behavior

No response

Logs

No response

Anything else?

No response

@tamlok tamlok added the bug Something isn't working label May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant