Re: colorscheme 16-bit

I always worry that some day there will be a newer version of a color scheme file and I'll lose fancy new colours this way. My solution is to create a custom file (such as mysolarized.vim) and source the original in there and just change the name and replace those colors that I want changed. 

I've gone pretty far with this and have a mycommon.vim and mycommonlight.vim and mycommondark.vim that I source from all my versions, the latter two depending on the value of &background.

--

Salman

On Fri, Apr 19, 2019, 14:52 meine <trialero@gmx.com> wrote:

Hi,

There are lot of great Vim colorschemes out there, but beware to use
one in a plain tty console -- it looks like nothing. Recently I adopted
switching relative and absolute line numbers, and that is where coloring
is important. In console most of us probably use a more basic
colorscheme, avoiding all the soft focus and tones that won't
display anyway.

Although most colorschemes in eg. vimcolors.org have a button to select
`Term' savvy schemes, almost all of them are 256 colors and not the 8 or
max 16 colors you have in a decent tty console. `Term' isn't the same as
a plain console without GUI.

This afternoon I did the following (to end frustration ;-):

1. download the colorscheme you like most, and put it in ~/.vim/colors/
Open the file in your preferred editor, and use it with `:color <myscheme>'

2. look for the lines with the parts that most annoy you in console. For
me it was LineNr, Comment and CursorLineNr. The first two where too dark
and the last one I wanted yellow instead of white (nighted.vim
scheme);

3. change the value of `ctermfg' to a 16-bit value that actually works.
Leave the rest that is fine; Search the Net for a `256colors2.pl' Perl
file that gives your console color numbers (top row 0-7, bottom row
8-15);

4. save (as) the changed colorscheme under the same name with eg. `_16b' on
the end to mark your changes;

5. test your adapted colorscheme with `:color <myscheme>_16b' and
evaluate your changes. Don't forget to change the naming of the
colorscheme in the top lines of the <myscheme>_16b.vim file: `let
g:colors_name = <newname_with_16b>'. This is improtant for proper
working in your `vimrc';

6. if it works, just add your `_16b' scheme to your .vimrc.

For me it works!

Happy Easter Weekend!

//meine

--
--
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.

--
--
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.