-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microsoft Windows Console Solarized color scheme #127
Comments
I'm on a semi submerged medieval city/island right now, sorry for reply
|
I made a copy and paste error above: [HKEY_tCURRENT_USER\Console\Cygwin Bash Shell - solarized] should be [HKEY_CURRENT_USER\Console\Cygwin Bash Shell - solarized] |
Have you maybe created the light version? |
Hello, I will be out of the office until August 25th. and cannot read your mail until then. Please contact Urs Gleim for urgent issues. Regards, Konrad Schwarz |
I believe the light version just uses different foreground and background colors from the same palette as the dark version. The Windows color command can be used to change the foreground and background color. See color /? My batch script solarized_light.bat does this: Accordingly, my batch script solarized_dark.bat contains: |
Hi,
this isn't an issue per se, but a first step towards a solarized Microsoft Windows Console.
This could be useful for running a solarized Vim, e.g., from the standard Cygwin console.
I sent largely the same content to Ethan Schoonover, but have not received a reply up to now;
to prevent this from being lost, I am reposting here.
The colors tab in the properties dialog box of a Windows Console allows one to change the colors
bound to the sixteen terminal color identifiers, so this can be used to set up the Solarized color map.
According to > color /?, Windows calls these 16 colors
0 = Black 8 = Gray
1 = Blue 9 = Light Blue
2 = Green A = Light Green
3 = Aqua B = Light Aqua
4 = Red C = Light Red
5 = Purple D = Light Purple
6 = Yellow E = Light Yellow
7 = White F = Bright White
The second colum is the is the light or bright version of the first.
Substituting Aqua -> Cyan and Purple -> Magenta, I entered the RGB values
from the table in section "The Values" on the Solarized home page into the Console's Color Tab on
the Properties page.
Windows stores these entries in its registry under a key depending on a command window's title.
Here are the values for a Window XP Console with title "Cygwin Bash Shell - solarized":
(I haven't figured out how to upload an attachment in github, so this is inlined.)
Windows Registry Editor Version 5.00
[HKEY_tCURRENT_USER\Console\Cygwin Bash Shell - solarized]
"ScreenColors"=dword:00000089
"PopupColors"=dword:000000fe
"ColorTable00"=dword:00423607
"ColorTable01"=dword:00d28b26
"ColorTable02"=dword:00009985
"ColorTable03"=dword:0098a12a
"ColorTable04"=dword:002f32dc
"ColorTable05"=dword:008236d3
"ColorTable06"=dword:000089b5
"ColorTable07"=dword:00d5e8ee
"ColorTable08"=dword:00362b00
"ColorTable09"=dword:00969483
"ColorTable10"=dword:00756e58
"ColorTable11"=dword:00a1a193
"ColorTable12"=dword:00164bcb
"ColorTable13"=dword:00c4716c
"ColorTable14"=dword:00837b65
"ColorTable15"=dword:00e3f6fd
"InsertMode"=dword:00000001
"QuickEdit"=dword:00000000
"FullScreen"=dword:00000000
"ScreenBufferSize"=dword:012c0050
"WindowSize"=dword:00530050
"FontSize"=dword:000c0000
"FontFamily"=dword:00000036
"FontWeight"=dword:00000190
"FaceName"="Lucida Console"
"CursorSize"=dword:00000064
"HistoryBufferSize"=dword:00000032
"NumberOfHistoryBuffers"=dword:00000004
"HistoryNoDup"=dword:00100000
The ColorTable[0-9][0-9] correspond to the 16 colors, ScreenColors and PopupColors
encode the foreground/background colors for normal and popup text in the two least-significant
nibbles.
The regedit GUI or the reg command line tool can be used to import the above file (with a .reg suffix)
into the Windows registry.
The console looks ok, however, Cygwin vim somehow resets the foreground color,
so that when I leave vim, my foreground color is messed up.
I don't have time to investigate this further at the moment. However, perhaps this could be of
interest to you.
The text was updated successfully, but these errors were encountered: