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
[macOS] Alacritty not tracking the left / right arrow key for IME.Preedit.cursor_byte_offset value changes. #7881
Comments
To me, the captured value
|
Why would anyone willingly use utf16? |
@chrisduerr I don't want, either. However, the g-damned InputMethodKit API deals with UTF16 NSRange. |
Well not winit's input method API, which is where the logs are from. So 21 makes sense here. |
@chrisduerr Then the question is: how Alacritty receive the 2nd parameter (NSRange) sent to IMKTextInput.setMarkedText ? |
All IME releated bit are abstracted in the windowing library we're using https://github.com/rust-windowing/winit |
@kchibisov Thank you so much. No wonder why I found nothing in Alacritty repo after using IMK API names as keywords. |
No wonder why things get messed up: Both |
I sent the issue ticket to |
[macOS] Alacritty not tracking the left / right arrow key for IME.Preedit.cursor_byte_offset value changes.
From the printed events below we can see that
IME.Preedit.cursor_byte_offset
is not updated on the events of left & right arrow keys.System
OS: Linux/BSD/macOS/Windows
Version:
alacritty --version
outputLinux/BSD: X11/Wayland, DE or Compositor and WM
Logs
Crashes: STDERR, STDOUT
Font/Terminal size:
alacritty -vv
Keyboard and bindings:
alacritty --print-events
printed events:
The text was updated successfully, but these errors were encountered: