- Windows terminal color scheme how to#
- Windows terminal color scheme full#
- Windows terminal color scheme windows 10#
DWINVER=0x0501 -D_WIN32_WINNT=0x0501 /MP -DHAVE_STDINT_H /Ox /GL -DNDEBUG /Zl /MT -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_MBYTE -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_TCL -DDYNAMIC_TCL -DDYNAMIC_TCL_DLL=\"tcl86t.dll\" -DDYNAMIC_TCL_VER=\"8.6\" Iproto -DHAVE_PATHDEF -DWIN32 -DFEAT_CSCOPE -DFEAT_TERMINAL -DFEAT_JOB_CHANNEL +conceal -footer +mouse +ruby/dyn -toolbarĢnd user vimrc file: "$HOME\vimfiles\vimrc"ĭefaults file: "$VIMRUNTIME\defaults.vim"Ĭompilation: cl -c /W3 /nologo -I. +comments +folding +modify_fname +rightleft +title +cmdline_info +float +mksession +reltime +timers -xterm_save +cmdline_hist +find_in_path +menu +quickfix +textobjects -xpm_w32 +cmdline_compl +file_in_path +lua/dyn +python3/dyn -termresponse -xim +clipboard +farsi +localmap +python/dyn -tgetent -xfontset +clientserver +extra_search +listcmds +profile +terminal +writebackup +cindent +ex_extra +lispindent +printer +termguicolors +windows +channel +eval +linebreak -postscript +tcl/dyn +wildmenu +byte_offset +emacs_tags +libcall +persistent_undo -tag_any_white +wildignore ++builtin_terms -ebcdic +langmap +perl/dyn +tag_old_static +vtp browse -dnd +lambda +path_extra +tag_binary +vreplace +balloon_eval_term +digraphs +keymap +packages +syntax +viminfo
balloon_eval +diff +jumplist +num64 -sun_workshop +visualextra +autoservername +dialog_con +job -netbeans_intg +statusline +visual
+autocmd +cursorbind +iconv/dyn +multi_lang +smartindent +vertsplit +arabic +cscope -hangul_input +multi_byte_ime/dyn +signs +vartabs +acl +cryptv +gettext/dyn -mouseshape +scrollbind +user_commands VIM - Vi IMproved 8.1 (2018 May 18, compiled 22:02:51)Ĭompiled by version without GUI. Now that I've solved that mistake I've got the following :version: :version I should have noticed that the Vim version was incorrect. I still had my system environment path pointing to my Git SCM installation C:\Program Files\Git\usr\bin (which contains an older version of Vim) and on top of that I had the same directory before my new Vim installation directory of C:\Program Files\vim\vim81 in the user environment path.
Windows terminal color scheme full#
Tl dr: My path was using the an old Vim version, with v8.1.428 we have full 24-bit glorious colours in Vim in the Windows Console! See below for screenshots.Įrr, so there was a basic mistake on my part. set t_Co=8 reduces the colour palette, where as set t_Co=16 and set t_Co=256 give the same result. Setting termguicolors changes all colours to white. This is what I've achieved so far, you can see the blatant issues with the Airline Theme colours but I'm not so bothered about that, I'm just trying to figure out what impact the termguicolors should have:Įdit: I have used the xterm-color-table.vim plugin to inspect what colours that I do have:
Windows terminal color scheme how to#
Changing the Vim colorscheme has no impact, the colours are almost entirely defined by the console colors.įor example the tender colorscheme is definitely 24-bit, but I cannot see how to get it to work with vim.exe in a dos/console prompt.ĭoes anyone have examples of how they have used termguicolors / 24-bit colorschemes in the Windows console?Įdit: I think I'm more asking is it possible to get a 256 colour colorscheme working in Vim in a DOS prompt? Even though you can choose from a palette of 24-bit colours, you can still only choose 16 of them" However termguicolors appears to make no difference and I cannot tell if a full 24-bit colour display is being used. I can get reasonable colours using the Console ColorTool. using vim.exe inside cmd.exe not gVim) using termguicolors.
Windows terminal color scheme windows 10#
The Windows 10 console now has 24-bit colours, and Vim 8 has been patched to handle 24-bit colours in the Windows console (i.e.
I'm using 64-bit Vim on Windows 10 release 1803.
0 kommentar(er)
