

There's no doubt it's about IME, which is why I was poking around the relevant lines linked above.īut nothing I do in Alacritty itself seems to fix it.īack to winit, I proceeded to revert this line again. While this line wasn't changed in that commit, I tested to disable IME by setting it to false. What I testedīecause these two lines ((), ()) were added in the Alacritty ( /issues/6817#issuecomment-1510439015), I tried commenting them out. The compiled app can be found inside the alacritty/target/release/osx directory. To clean up between each test, I use make clean, then make app again.

Which really is just running make app in the alacritty directory.
Alacritty m1 manual#
Then do the changes I'd like to test, and follow the manual installation instructions outlined here. I then switch the winit reference in both alacritty/alacritty/Cargo.toml and alacritty/alacritty_config/Cargo.toml from I clone both winit and Alacritty, alongside each other.
Alacritty m1 install#
I wrote down the things I tested, if it's of use to anyone Steps I used to install and compile things on macOS
Alacritty m1 code#
Rust, developing terminals, IME, etc, isn't really my cup of tea, but I tried poking around the code a bit, testing things. I only ever have a single layout added at a time, but always with Figs input method installed.Īll of them works correctly if I uninstall the Fig input method.Ĭontrary to what I mentioned before, I do have to restart Alacritty after re-installing Figs input method. So I don't need to switch layouts, or so - just tap one of them and all keys are again available for me. ), using special characters like ´, ¨, ~ will make it possible to type anything again. Irrespective of layout I've tested (US, US International, British, Canadian, Finnish, Swedish, Norwegian, German. That's about as helpful as I could possibly be, unfortunately, as I'm not super-familiar in this area, nor fluent in Rust.

This was also tested against Alacrittys latest master, which works with that line reverted. With the other change/added line in that commit, it still works. Reverting this line, specifically, it starts working again.

Alacritty m1 update#
I tried bisecting both winit and Alacritty alongside each other, to try and get a rough pointer on where it happens.Īs the commit message in my 2nd edit is an update to winit 0.28.0, that's what I picked as a bad commit.Įventually I got to the 3fd7384 commit, where it started breaking again. I've tested on both an intel 2019 MacBook Pro, and an M1 2022 MacBook Pro, if that'd matter.Īfter a bisect, 1c878a0 is the commit where it starts breaking for me. It's still temporarily resolved by changing keyboard layout, as others have mentioned.Īlacritty v0.11.0 works for me, but Alacritty v0.12.0-rc1 does not. Whenever I uninstall the Fig input method, Alacritty works.įor uninstalling I need to restart Alacritty, but when installing the Fig input method it breaks immediately. I only have one keyboard layout, but do have Fig and its input method (for the completion popup). TMPDIR=/var/folders/my/gzz9nv7x0wq45khvl83pv4br0000gn/T/įor those text input in Alacritty works for, do you have more than one input method? SSH_AUTH_SOCK=/private/tmp/0HBpvq/Listeners PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/usr/local/share/dotnet:~/.dotnet/tools:/Library/Apple/usr/bin:/Library/Frameworks/amework/Versions/Current/Commands:/Applications/Wireshark.app/Contents/MacOS:/Applications/Postgres.app/Contents/Versions/latest/bin:/Users/home/.cargo/bin:/Users/home/.fig/bin:/Users/home/.local/bin NNN_PLUG=f:finder o:fzopen p:preview-tui d:diffs v:imgview m:mimelist
