-
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
terminfo details missing on macOS #2131
Comments
Some prior discussion was made in #1630. Checking quickly through everything, it almost looks to me like the capabilities that are not included without the If this would be the case, chances are that applications like Taking a look at the build files for Termite in the Archlinux repository, you can see that this does indeed use the |
FYI: on my machine, I don't see any (obvious) breakage of the |
This has been a long time ago, but I believe the issues were likely related to clicking of the columns to sort them and clicking on different rows to select them. With the current terminfo this should work great (it does on my machine), but iirc it broke with the |
Ah, yes, you are correct, it does break (in interesting ways, I might add 😄). FYI, in tmux, both set -g default-terminal "tmux-256color"
# set -g default-terminal "alacritty"
set -ga terminal-overrides ",alacritty:Tc" |
Well, using the |
@chrisduerr true, but what I found interesting about that is that the cursor style changing still works as expected. So: using |
The problem with Neovim's cursor style is not Alacritty's support for it. If any program ever sends the right escapes, Alacritty will parse them properly and apply them. The problem is that these escapes are never sent if the terminfo is incorrect. So keeping the |
To make sure all extended capabilities can be queried correctly, it is necessary to compile the terminfo file using the `-x` flag. Since Alacritty specified support for the XTerm mouse mode (XM/xm), using the `-x` flag was not possible until now without breaking programs like `htop`. By removing this flag, these issues should be resolved. This fixes alacritty#2131.
@JeanMertz Would you mind testing if you can find any issues with the new terminfo file provided in #2134? |
To make sure all extended capabilities can be queried correctly, it is necessary to compile the terminfo file using the `-x` flag. Since Alacritty specified support for the XTerm mouse mode (XM/xm), using the `-x` flag was not possible until now without breaking programs like `htop`. By removing this flag, these issues should be resolved. This fixes alacritty#2131.
To make sure all extended capabilities can be queried correctly, it is necessary to compile the terminfo file using the `-x` flag. Since Alacritty specified support for the XTerm mouse mode (XM/xm), using the `-x` flag was not possible until now without breaking programs like `htop`. By removing this flag, these issues should be resolved. This fixes #2131.
I can confirm that it does work on MacOS, my version is Mojave 10.14.4, just a heads up if someone follow these instructions and it still does not work. Make sure your |
The installation instructions mention running:
to install the Alacritty specific terminfo definitions.
However, this does not (always) seem to be enough to get cursor style support to work, specifically in tmux.
The solution for me was to add the
-x
flag totic
:However, it appears this is not the final solution, as it apparently changes the behavior of Alacritty.
This is happening with the following software versions:
The text was updated successfully, but these errors were encountered: