Christian Brabandt wrote:
> On So, 05 Apr 2020, Bram Moolenaar wrote: > > > > > Patch 8.2.0518 > > Problem: A terminal falls back to setting $TERM to "xterm". > > Solution: Use "xterm-color" if more than 16 colors are supported and > > "xterm-256color" if at least 256 colors are supported. > > (closes #5887) > > Files: src/os_unix.c > > Should we also use xterm-direct if xterm supports RGB coloring? I > believe this is the new terminfo entry for xterm with RGB support. That is exactly the problem: If we use xterm-direct on a system that doesn't have this entry, it will fail completely. I'm not sure if there is a good (efficient) way to check for a working entry. Might be that loading it is needed, which might be slow. Perhaps we should just check if $TERM is set to "xterm-.*" and use that in the terminal too. But when $TERM is "screen-*" or "iterm-*" we can't. -- Why I like vim: > I like VIM because, when I ask a question in this newsgroup, I get a > one-line answer. With xemacs, I get a 1Kb lisp script with bugs in it ;-) /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/202004141816.03EIGOod024052%40masaka.moolenaar.net.
