-
Notifications
You must be signed in to change notification settings - Fork 3k
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 Big Sur shell and tty strange behaviors with inputs #5023
Comments
Sounds like an issue with your macOS setup. I'd recommend looking into keyboard layout, potentially configured global shortcuts and the output of the |
I tried to use different keyboard layouts but same issue on this character. What do I have to do with the locale command ?
Also I don't understand because in the default shell open by Alacritty, the keys are working perfectly.. |
Try setting the locale to |
I can try but the In the default term
in the sub-term (/bin/bash):
Also, this is the locale output from a working terminal emulator (Terminal.app):
EDIT: I tried to run alacritty with the print-events flag and I found this in the logs:
EDIT 2: I also tried to change the locale using the LC_ALL env variable and run shell using the --login flag in the alacritty configuration file but still not working..
|
If this works just fine, I'd assume zsh is your default shell? Have you tried changing your shell to |
My default shell is fish actually, I tried to set the shell used by alacritty to zsh and bash but the keys are not working as expected also... |
Well then try with your default shell set to |
Nothing to do, same issue, I do not manage to make the keys working as expected...
So I rolled back to fish.. I fact, it seems only fish is working. I can open a sub-fish shell session and it works, but any other shells are not working with my alacritty.. |
So launching |
Exactly, only fish inside fish works. All the other combinations except
I can start them, bit when I want to use some keys like '{', I have several behaviors (nothing, directory listing...) in alacritty. Those combinations seem to be working well with the default Terminal.app included with MacOS. Infos: my Mac is configured with French keyboard layout, and I'm using an AZERTY keyboard. |
Does it work with qwerty? Probably a duplicate of #458. |
Yes it works with Qwerty layout, so it seems to be a duplicated issue |
It seems somewhat strange that it would cause the behavior you've described, but I doubt there's any issue in Alacritty besides the qwerty layout one. Hopefully once that is finally resolved things will either work properly or at least help troubleshoot this issue further. |
System
OS: MacOS BigSur 11.3
Version: alacritty 0.7.2 (5ac8060)
Description
I have an issue with my alacritty when I'm using a new shell session. I can start the session, but then, some inputs are behaving in a strange way while in normal mode it's working well. For example, if I try to type a
{
, in some tty it's not working at all, and in other, it displays the current directory content in formatted way :In my Alacritty env,
TERM=alacritty
.I tried to use these commands in an other terminal emulator (default MacOS one) and it works well, the inputs are corrects.
Do not hesitate to ask me for more details if you need to.
Thanks
The text was updated successfully, but these errors were encountered: