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.
--
CONCORDE: Message for you, sir.
He falls forward revealing the arrow with the note.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- Bram@Moolenaar.net -- 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_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 vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment