MacOS – From where do the encodings supported by Terminal come

Well, these commands edit .plist files in your /Users/xyz/Library/Preferences folder. So, if you look at these files, you can look at these files and base your Terminal commands after these.

These are XML-based files, so you can view them in a more readable format if you open them in Xcode, which is available in the Mac App Store.

In the Terminal, the format for these is "defaults write PLIST_FILE KEY -TYPE VALUE" where the PLIST_FILE is the name of the file in the Preferences folder without the .plist, KEY is the key that you can see in Xcode, -TYPE is the type of key that you can find Xcode (and you can find if there is an abbreviation for that type by typing "defaults" into the terminal), and value is the value you wish to set the key at.

Here are some of the string types from the Terminal:

-string <string_value>
-data <hex_digits>
-int[eger] <integer_value>
-float  <floating-point_value>
-bool[ean] (true | false | yes | no)
-date <date_rep>
-array <value1> <value2> ...
-array-add <value1> <value2> ...
-dict <key1> <value1> <key2> <value2> ...
-dict-add <key1> <value1> ...

The problem is likely due to your vim settings rather than your terminal settings.

The color you mentioned is pretty close to color 224 (of 256 colors), so you might try looking in your vim colorscheme to see if that color is used in a ctermfg= declaration.

To test and see if I'm right you could try

:syn match Foo /foo/
:hi Foo ctermfg=red

If that turns the word foo red then you know your terminal's red is working properly and it will be an issue with your vim settings.