2018年4月30日月曜日 23時21分36秒 UTC+8 Bram Moolenaar: > Christian wrote: > > > On Mo, 30 Apr 2018, Bram Moolenaar wrote: > > > > > Masaaki Nakamura wrote > > > > > > > Thanks to the patch 8.0.1685, the output in terminal buffers got easy > > > > to see in any colorscheme. I'm really happy with it. > > > > > > > > Now, I would like to set "g:term_ansi_colors" in my colorscheme file, > > > > but then I'm wondering it could be harmful for other colorschemes. For > > > > example, first I set my colorscheme A and then change to another > > > > colorscheme B, the "g:term_ansi_colors" set by A may not match with B. > > > > > > > > At first, I can use "ColorScheme" autocmd event to restore the default > > > > colors. However, it is triggered after the colorscheme B sorced. If B > > > > also wants to set its "g:term_ansi_colors", it might be overwritten > > > > unintentionally. > > > > > > > > Anyone has ideas to restore the default colors? Or it is not expected > > > > to be set in a colorscheme file? > > > > > > I don't think there is an easy way. I can add the ColorSchemePre > > > autocommand event. > > > > Shouldn't syncolor and nosyntax reset g:term_ansi_colors? > > g:term_ansi_colors is about the colors, not the syntax. Thus it's > related to highlighting. > > syncolor.vim is a bit of a corner case, since it can set and reset the > colors used for syntax highlighting. But I don't see how this matters > for the colors to be used in a terminal (which may have nothing to do > with syntax highlighting). >
I see. Since we executes ":syntax reset" at the top of a colorscheme file, I thought good idea, but, indeed, it is not syntax. I built the latest vim and ColorSchemePre works as I want. Thanks you. -- -- You received this message from the "vim_use" 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_use" 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.
