bfredl
bfredl
the documentation for 'termguicolors' is actively misleading, the option defaults to on and not off. > nvim --clean --cmd "echo synIDattr(synIDtrans(hlID('string')),'fg')" shows the GUI color name. This is the **expected**...
I think that particular inconsistency can be observed since https://github.com/neovim/neovim/pull/26579
should we maybe place the files under `src/nvim/tui/` if it is just part of the TUI and not seen as a separate library?
yes, and it is going to be a while until we do a replacement anyway. Doing refactors on the level of fixing warnings and deleting dead code is worth it...
https://github.com/afnanenayet/diffsitter this also looks interesting as it is based on tree-sitter.
likely there is a disagreement of character width between libvterm and neovim screen renderer
has @leonerd been made aware of the libvterm patch? https://github.com/vim/vim/commit/4549dad874244fe933b969e4ac0b41923ee70dc3#diff-acc4f584e08c59495b7607a987ef4f9b7c23affc796acf404d4eded5fabe54fe
Is that just not the shell highlighting a missing final newline?
@yatli > It seems that the neovim is sticking to an older standard (perhaps 9.0? according to some fragments of code and comments I saw), The unicode tables are up...
Weird, 0x2764 is part of `emoji-data.txt` (and `intable(emoji_all, ARRAY_SIZE(emoji_all), 0x2764)` return true). It it supposed to become wide by either 'ambiwith' or 'emoji' (depending on if it was "ambiguous" or...