unibi_from_term: make $TERMINFO behavior compatible to curses #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kitty e.g. sets `$TERMINFO` (at least when using the development version), but it only contains its own entry for xterm-kitty. When you start tmux then from there, tmux uses this `$TERMINFO` variable, and then Neovim would fail to parse `TERM=screen` properly (via `unibi_from_term`) then. Fixes mauke#36.
This was referenced Jun 22, 2019
This was referenced Aug 3, 2019
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
kitty e.g. sets
$TERMINFO(at least when using the development version),but it only contains its own entry for xterm-kitty.
When you start tmux then from there, tmux uses this
$TERMINFOvariable,and then Neovim would fail to parse
TERM=screenproperly (viaunibi_from_term) then.Fixes mauke#36.