On Sun, Mar 18, 2018 at 5:04 PM, Kazunobu Kuriyama < [email protected]> wrote:
> 2018-03-19 5:25 GMT+09:00 Manuel Ortega <[email protected]>: > >> >> >> Finally, another reason to not put "!" in &cpo by default just yet is >> that the colors are hard to read if your colorscheme has a black or nearly >> black background. This is *not* a MacVim specific problem. There is an >> open thread about this on GitHub, I think. Maybe that should be solved >> before making "!cmd" result in nigh-invisible output. >> > > That is rather a well-known, classic issue that blue is hardly visible on > a dark background color, as is written in the comment of > app-defaults/XTerm-color. That has happened with color consoles as well. > Perhaps we could "correct" the pixel values of blue (color4) and light blue > (color12) just like the XTerm-color comment suggests, but there seems to be > pros and cons as to what values are better than the current ones. Anyway, > it is the fact that xterm has been shipped with them and that nobody has > never stopped it. > One disanalogy here is that if the default colors of one's terminal emulator (e.g., Terminal.app) are unreadable, *one can change them easily*. That is not the case of the colors that appear in a vim `:terminal`, whether in the GUI or not. There's no vim setting for making that blue lighter. All you can do (I assume) is manually edit some source code before compiling. On some github thread there's discussion of making this changeable. I really hope it gets done. -Manny -- -- 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]. For more options, visit https://groups.google.com/d/optout.
