I'm seeing a complete failure of the "colorscheme" function to perform syntax highlighting. On a virtual machine that hasn't seen the update that breaks things, I'm able to confirm a version where it's previously working: vim-common-9.1.1972-1.fc43.x86_64 And the version where it seems to be broken (it either has no color scheme at all, or makes everything only one of the colors in the scheme; for "elflord", it makes everything cyan): vim-common-9.1.2128-2.fc43.x86_64 On opening an existing file, it silently fails, but if I run a "colorscheme" command, I can see an error, as detailed in the steps to reproduce. Reproducible: Always Steps to Reproduce: 1. Run "vi <filename>" to open a file. (Perhaps using the "vi" command is a factor here; running "vim <filename>" seems to correctly load a colorscheme.) 2. Execute the "colorscheme" command to manually load a colorscheme. Example: :colorscheme elflord Actual Results: Error detected while processing /usr/share/vim/vim91/colors/elflord.vim: line 13: E319: Sorry, the command is not available in this version: let g:colors_name = ' elflord' line 15: E319: Sorry, the command is not available in this version: let s:t_Co = has('gui _running') ? 16777216 : str2nr(&t_Co) line 16: E319: Sorry, the command is not available in this version: let s:tgc = has('term guicolors') && &termguicolors line 18: E319: Sorry, the command is not available in this version: let g:terminal_ansi_c olors = ['#000000', '#cd0000', '#00cd00', '#cdcd00', '#0000ee', '#cd00cd', '#00c dcd', '#e5e5e5', '#7f7f7f', '#ff0000', '#00ff00', '#ffff00', '#5c5cff', '#ff00ff ', '#00ffff', '#ffffff'] (Additionally, the editor text is all either uncolored, or may be one of the colors of the colorscheme that failed to load. For my example above of using "elflord", I've seen cases where the text is all cyan, therefore probably matching the RGB color code of "#00ffff".) Expected Results: The colorscheme loads properly, and accurately changes text color according to the syntax of the file type loaded.
Hi Bryan, I'm sorry for inconvenience - the alias was brought back by https://bodhi.fedoraproject.org/updates/FEDORA-2026-36e120e597 . Anyway, thank you for providing the command you used - you are the first one to do it, others mentioned only "start Vim", but they did not call 'vim' on command linebut 'vi' :) Although 'vi' is Vim project built with tiny features (to simulate as much as possible the old Vi functionality), it does not include common Vim features like colorscheme/encryption/syntax highlight etc. I thought users type 'vim' if they want 'vim', but I was proven wrong. *** This bug has been marked as a duplicate of bug 2439657 ***