LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   Vim : Warning: Color name "BACKGROUND" is not defined (https://www.linuxquestions.org/questions/linux-software-2/vim-warning-color-name-background-is-not-defined-4175464494/)

PasBern 06-02-2013 04:24 PM

Vim : Warning: Color name "BACKGROUND" is not defined
 
When I exit a file view with or edited with vim, I receive the following warning notice:
Code:

Warning: Color name "BACKGROUND" is not defined
I does not matter whether use vim as regular user or as root. I could not find any mention of a variable BACKGROUND in any .vimrc, .viminfo or .vim_colorv_cache_fav file.

I'm on Sabayon Linux 11 with vim (7.3.905) and vim-core (7.3.905) installed.

This seems to be a very rare issue, so far I have not found a solution, let alone even a post, or site mentioning the problem at all. I thought the problem had magically gone away when I correct my local setting back to en_US.UTF-8 after some update messed that up and changed it to POSIX, for one or two days the warning had disappeared. Unforunately no longer. I cannot remember changing anything on my system during these 'happy' days, that could have made this behavior come back.

TobiSGD 06-02-2013 04:26 PM

Try to change your colorscheme and see if the problem disappears.

PasBern 06-03-2013 05:14 AM

Unfortunately changing the color scheme does not solve the problem. I still get the same warning. :cry:

TobiSGD 06-03-2013 07:07 AM

This may also be an Xterm issue (if you are using Xterm). Do you have the same issues when using an alternative terminal emulator, like Gnome terminal or Konsole?

PasBern 06-03-2013 09:58 AM

Quote:

Originally Posted by TobiSGD (Post 4964533)
This may also be an Xterm issue (if you are using Xterm). Do you have the same issues when using an alternative terminal emulator, like Gnome terminal or Konsole?

I thought of that too, as when you suggested to change the color scheme I was not sure whether you meant the color scheme of vim or that of the terminal emulator.

I always get this warning when opening a file with vim in a GUI terminal (GNOME Terminal, MATE Terminal, Konsole, UXTerm, XTerm, LXTerm - I tried them all, and always the same behavior). Then I switched to the 'real' console via ALT+CTRL+F2 and there vim works just fine. Apparently I has nothing to do with a certain terminal emulator, but rather with vim working together with a graphical desktop environment (Or the other way around :-). Currently I'm using the MATE desktop, I will log out and see if the same happens in KDE, or XFCE.

PasBern 06-03-2013 10:23 AM

I just tried using vim in KDE, Gnome-Shell & Cinnamon, and still vim complains that the BACKGROUND color is not defined.... :(

TobiSGD 06-03-2013 10:26 AM

Then I am out of ideas.

PasBern 06-04-2013 04:17 AM

Quote:

Originally Posted by TobiSGD (Post 4964637)
Then I am out of ideas.

Thanks anyways :hattip:

Apparently this is a tricky issue, as I seem to be the only one having this problem.

Habitual 06-04-2013 08:19 AM

post your ~/.vimrc?

PasBern 06-05-2013 02:01 AM

This is the global vimrc in /etc/vim, there were no .vimrc-files neither in my home directory nor in root's. I downloaded a sample from here http://amix.dk/vim/vimrc.html and sourced it, does not make a difference.

vimrc:

Code:

scriptencoding utf-8
" ^^ Please leave the above line at the start of the file.

" Default configuration file for Vim
" $Header: /var/cvsroot/gentoo-x86/app-editors/vim-core/files/vimrc-r4,v 1.3 2010/04/15 19:30:32 darkside Exp $

" Written by Aron Griffis <agriffis@gentoo.org>
" Modified by Ryan Phillips <rphillips@gentoo.org>
" Modified some more by Ciaran McCreesh <ciaranm@gentoo.org>
" Added Redhat's vimrc info by Seemant Kulleen <seemant@gentoo.org>

" You can override any of these settings on a global basis via the
" "/etc/vim/vimrc.local" file, and on a per-user basis via "~/.vimrc". You may
" need to create these.

" {{{ General settings
" The following are some sensible defaults for Vim for most users.
" We attempt to change as little as possible from Vim's defaults,
" deviating only where it makes sense
set nocompatible        " Use Vim defaults (much better!)
set bs=2                " Allow backspacing over everything in insert mode
set ai                  " Always set auto-indenting on
set history=50          " keep 50 lines of command history
set ruler              " Show the cursor position all the time

set viminfo='20,\"500  " Keep a .viminfo file.

" Don't use Ex mode, use Q for formatting
map Q gq

" When doing tab completion, give the following files lower priority. You may
" wish to set 'wildignore' to completely ignore files, and 'wildmenu' to enable
" enhanced tab completion. These can be done in the user vimrc file.
set suffixes+=.info,.aux,.log,.dvi,.bbl,.out,.o,.lo

" When displaying line numbers, don't use an annoyingly wide number column. This
" doesn't enable line numbers -- :set number will do that. The value given is a
" minimum width to use for the number column, not a fixed size.
if v:version >= 700
  set numberwidth=3
endif
" }}}

" {{{ Modeline settings
" We don't allow modelines by default. See bug #14088 and bug #73715.
" If you're not concerned about these, you can enable them on a per-user
" basis by adding "set modeline" to your ~/.vimrc file.
set nomodeline
" }}}

" {{{ Locale settings
" Try to come up with some nice sane GUI fonts. Also try to set a sensible
" value for fileencodings based upon locale. These can all be overridden in
" the user vimrc file.
if v:lang =~? "^ko"
  set fileencodings=euc-kr
  set guifontset=-*-*-medium-r-normal--16-*-*-*-*-*-*-*
elseif v:lang =~? "^ja_JP"
  set fileencodings=euc-jp
  set guifontset=-misc-fixed-medium-r-normal--14-*-*-*-*-*-*-*
elseif v:lang =~? "^zh_TW"
  set fileencodings=big5
  set guifontset=-sony-fixed-medium-r-normal--16-150-75-75-c-80-iso8859-1,-taipei-fixed-medium-r-normal--16-150-75-75-c-160-big5-0
elseif v:lang =~? "^zh_CN"
  set fileencodings=gb2312
  set guifontset=*-r-*
endif

" If we have a BOM, always honour that rather than trying to guess.
if &fileencodings !~? "ucs-bom"
  set fileencodings^=ucs-bom
endif

" Always check for UTF-8 when trying to determine encodings.
if &fileencodings !~? "utf-8"
  " If we have to add this, the default encoding is not Unicode.
  " We use this fact later to revert to the default encoding in plaintext/empty
  " files.
  let g:added_fenc_utf8 = 1
  set fileencodings+=utf-8
endif

" Make sure we have a sane fallback for encoding detection
if &fileencodings !~? "default"
  set fileencodings+=default
endif
" }}}

" {{{ Syntax highlighting settings
" Switch syntax highlighting on, when the terminal has colors
" Also switch on highlighting the last used search pattern.
if &t_Co > 2 || has("gui_running")
  syntax on
  set hlsearch
endif
" }}}

" {{{ Terminal fixes
if &term ==? "xterm"
  set t_Sb=^[4%dm
  set t_Sf=^[3%dm
  set ttymouse=xterm2
endif

if &term ==? "gnome" && has("eval")
  " Set useful keys that vim doesn't discover via termcap but are in the
  " builtin xterm termcap. See bug #122562. We use exec to avoid having to
  " include raw escapes in the file.
  exec "set <C-Left>=\eO5D"
  exec "set <C-Right>=\eO5C"
endif
" }}}

" {{{ Filetype plugin settings
" Enable plugin-provided filetype settings, but only if the ftplugin
" directory exists (which it won't on livecds, for example).
if isdirectory(expand("$VIMRUNTIME/ftplugin"))
  filetype plugin on

  " Uncomment the next line (or copy to your ~/.vimrc) for plugin-provided
  " indent settings. Some people don't like these, so we won't turn them on by
  " default.
  " filetype indent on
endif
" }}}

" {{{ Fix &shell, see bug #101665.
if "" == &shell
  if executable("/bin/bash")
    set shell=/bin/bash
  elseif executable("/bin/sh")
    set shell=/bin/sh
  endif
endif
"}}}

" {{{ Our default /bin/sh is bash, not ksh, so syntax highlighting for .sh
" files should default to bash. See :help sh-syntax and bug #101819.
if has("eval")
  let is_bash=1
endif
" }}}

" {{{ Autocommands
if has("autocmd")

augroup gentoo
  au!

  " Gentoo-specific settings for ebuilds.  These are the federally-mandated
  " required tab settings.  See the following for more information:
  " http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml
  " Note that the rules below are very minimal and don't cover everything.
  " Better to emerge app-vim/gentoo-syntax, which provides full syntax,
  " filetype and indent settings for all things Gentoo.
  au BufRead,BufNewFile *.e{build,class} let is_bash=1|setfiletype sh
  au BufRead,BufNewFile *.e{build,class} set ts=4 sw=4 noexpandtab

  " In text files, limit the width of text to 78 characters, but be careful
  " that we don't override the user's setting.
  autocmd BufNewFile,BufRead *.txt
        \ if &tw == 0 && ! exists("g:leave_my_textwidth_alone") |
        \    setlocal textwidth=78 |
        \ endif

  " When editing a file, always jump to the last cursor position
  autocmd BufReadPost *
        \ if ! exists("g:leave_my_cursor_position_alone") |
        \    if line("'\"") > 0 && line ("'\"") <= line("$") |
        \        exe "normal g'\"" |
        \    endif |
        \ endif

  " When editing a crontab file, set backupcopy to yes rather than auto. See
  " :help crontab and bug #53437.
  autocmd FileType crontab set backupcopy=yes

  " If we previously detected that the default encoding is not UTF-8
  " (g:added_fenc_utf8), assume that a file with only ASCII characters (or no
  " characters at all) isn't a Unicode file, but is in the default encoding.
  " Except of course if a byte-order mark is in effect.
  autocmd BufReadPost *
        \ if exists("g:added_fenc_utf8") && &fileencoding == "utf-8" &&
        \    ! &bomb && search('[\x80-\xFF]','nw') == 0 && &modifiable |
        \      set fileencoding= |
        \ endif

augroup END

endif " has("autocmd")
" }}}

" {{{ vimrc.local
if filereadable("/etc/vim/vimrc.local")
  source /etc/vim/vimrc.local
endif
" }}}

" vim: set fenc=utf-8 tw=80 sw=2 sts=2 et foldmethod=marker :

Is there something that points to the problem?

murugesandins 04-16-2024 06:05 AM

I was trying to reproduce your issue using CYGWIN_NT at windows.
Initial content of ~/.vimrc:
Code:

set nu
syntax on

I have modified this file to have following content:
Code:

set nu
colorscheme BACKGROUND
syntax on

After this I am able to reproduce your error:
Code:

$ /usr/bin/vim.exe ~/.vimrc
Error detected while processing /home/murugesnadins/.vimrc:
line    2:
E185: Cannot find color scheme 'BACKGROUND'
Press ENTER or type command to continue

Hence I deleted following line at ~/.vimrc file:
Code:

colorscheme BACKGROUND
I tried the same using:
/etc/vimrc file at cygwin
Initial content of /etc/vimrc:
end of the file
Code:

" Source a global configuration file if available
if filereadable("/etc/vimrc.local")
  source /etc/vimrc.local
endif

After modification:
Code:

" Source a global configuration file if available
if filereadable("/etc/vimrc.local")
  source /etc/vimrc.local
endif
colorscheme BACKGROUND

Code:

$ /usr/bin/vim delete_array.cpp
/usr/bin/vim delete_array.cpp
Error detected while processing /etc/vimrc:
line  129:
E185: Cannot find color scheme 'BACKGROUND'
Press ENTER or type command to continue

Handle those exceptions using related find.
Code:

$ /usr/bin/find /etc/ -type f -name vim* -exec /usr/bin/grep -l "colorscheme.*BACKGROUND" {} \;
/etc/vimrc
$ /usr/bin/find ~/ -maxdepth 1 -type f -name .vim* -exec /usr/bin/grep -l "colorscheme.*BACKGROUND" {} \;



All times are GMT -5. The time now is 04:38 PM.