You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In macOS Sequoia, new hotkeys for window management (fn + control + arrow keys) have been introduced, and these work seamlessly across most applications. However, in the Alacritty, which relies on winit for its window handling, these shortcuts do not perform as expected.
Problem Details:
Expected Behavior: When using the shortcut fn + control + left, the Alacritty window should move to the left side of the screen.
Actual Behavior: Instead of moving the window, a sequence ([1;5H when pressing fn + control + left, [1;5F for fn + control + right, etc.) appears within the terminal.
This issue does not occur in other applications on the system, making it unclear whether this is a bug in Alacritty itself or an interaction with winit.
I have noticed the applications that accept fn+ctrl+arrow-key have this in the menu:
And it is not just Alacritty or winit applications, but another notable example is Parallels 19, which also does not have a Window menu, and similarly will not respond to these key combinations.
Ah, then the issue isn't in Winit per-say, it's that this kind of windowing functionality requires that you create menu items. Another example is that Command ⌘ + M to minimize doesn't work by default, since the relevant menu item isn't available.
I would recommend that you use the muda crate, and file an issue with them that they're missing these predefine menu items.
Description
In macOS Sequoia, new hotkeys for window management (fn + control + arrow keys) have been introduced, and these work seamlessly across most applications. However, in the Alacritty, which relies on winit for its window handling, these shortcuts do not perform as expected.
Problem Details:
This issue does not occur in other applications on the system, making it unclear whether this is a bug in Alacritty itself or an interaction with winit.
Could this issue be related to winit?
refer to #8209
macOS version
Winit version
0.30.4
The text was updated successfully, but these errors were encountered: