Loading ...
Sorry, an error occurred while loading the content.

78225Re: hi Comment guifg=white guibg=black in ~/.vimrc ignored

Expand Messages
  • Mark Woodward
    Mar 3, 2007
    • 0 Attachment
      Hi Tony,

      On Fri, 2007-03-02 at 10:52 +0100, A.J.Mechelynck wrote:
      > Mark Woodward wrote:
      > > Hi alex,
      > >
      > > On Thu, 2007-03-01 at 16:33 +0100, Alexander Farber wrote:
      > >> Hello Hugh,
      > >>
      > >> On 3/1/07, Hugh Sasse <hgs@...> wrote:
      > >>> :scriptnames
      > >> 1: C:\Documents and Settings\afarber\.vimrc
      > >> 2: C:\Program Files\Vim\vim70\syntax\syntax.vim
      > >> 3: C:\Program Files\Vim\vim70\syntax\synload.vim
      > >> 4: C:\Program Files\Vim\vim70\syntax\syncolor.vim
      > >> 5: C:\Program Files\Vim\vim70\filetype.vim
      > >> 6: C:\Program Files\Vim\vim70\menu.vim
      > >> 7: C:\Program Files\Vim\vim70\autoload\paste.vim
      > >> 8: C:\Program Files\Vim\vim70\plugin\getscript.vim
      > >> 9: C:\Program Files\Vim\vim70\plugin\gzip.vim
      > >> 10: C:\Program Files\Vim\vim70\plugin\matchparen.vim
      > >> 11: C:\Program Files\Vim\vim70\plugin\netrwPlugin.vim
      > >> 12: C:\Program Files\Vim\vim70\plugin\rrhelper.vim
      > >> 13: C:\Program Files\Vim\vim70\plugin\spellfile.vim
      > >> 14: C:\Program Files\Vim\vim70\plugin\tarPlugin.vim
      > >> 15: C:\Program Files\Vim\vim70\plugin\tohtml.vim
      > >> 16: C:\Program Files\Vim\vim70\plugin\vimballPlugin.vim
      > >> 17: C:\Program Files\Vim\vim70\plugin\zipPlugin.vim
      > >> 18: C:\Program Files\Vim\vim70\syntax\actionscript.vim
      > >
      > > Is this Vim or gVim?
      > > If the later, where's the .gvimrc file?
      > > If the former, putting guifg=... in the .vimrc is meaningless.
      > >
      > > If you're using gVim create a .gvimrc file in the same directory as
      > > the .vimrc. Place the guifg=... stuff in there.
      > >
      > > What is the output of scriptnames now?
      > > Is the syntax as you'd like it now?
      > >
      > >
      > > cheers,
      > >
      > >
      >
      > It's perfectly possible to run gvim with no gvimrc (it does source the vimrc).
      > ":highlight" commands would sit better in a colorscheme, but regardless of
      > whether they're in a colorscheme or in the vimrc, it's possible to set both
      > cterm[bf]g= and gui[bf]g= (and term= if deemed necessary) in the same ":hi"
      > command.
      >
      > IIUC, ":syntax on" resets all colors, re-invoking the current colorscheme if
      > any: thus it's usually less problematic to define colors in a colorscheme.
      > (When default colors are OK, the corresponding highlight groups can be omitted.)
      >
      > See (attached) an example colorscheme, which is the one I use for my
      > day-to-day editing. It may help you design your own. To use this one, drop it
      > in ~/.vim/colors and add
      >
      > colorscheme almost-default
      >
      > to your vimrc.
      >
      >
      > Best regards,
      > Tony.

      I agree gui hi can be set in the _vimrc file. However:

      However when I enter ":verbose hi Comment" I get:

      Comment xxx term=bold ctermfg=1 guifg=Blue
      Last set from C:\Program Files\Vim\vim70\syntax\syncolor.vim

      If the OP had a _gvimrc file it would be sources after the runtime
      syntax files:

      /home/mark/.vimrc
      /home/mark/.vim/filetype.vim
      /usr/local/share/vim/vim70/filetype.vim
      /home/mark/.vim/ftdetect/ruby.vim
      /usr/local/share/vim/vim70/menu.vim
      /usr/local/share/vim/vim70/autoload/paste.vim
      /home/mark/.vim/after/filetype.vim
      /usr/local/share/vim/vim70/ftplugin.vim
      /usr/local/share/vim/vim70/indent.vim
      /usr/local/share/vim/vim70/syntax/syntax.vim
      /usr/local/share/vim/vim70/syntax/synload.vim
      /usr/local/share/vim/vim70/syntax/syncolor.vim <<<<<<<<<<<<<<<<<
      /home/mark/.vim/plugin/curr_word.vim
      /home/mark/.vim/plugin/imaps.vim
      /home/mark/.vim/plugin/matchit.vim
      /home/mark/.vim/plugin/netrwPlugin.vim
      /home/mark/.vim/plugin/project.vim
      /home/mark/.vim/plugin/rails.vim
      /home/mark/.vim/plugin/rcodetools.vim
      /home/mark/.vim/plugin/taglist.vim
      /usr/local/share/vim/vim70/plugin/getscript.vim
      /usr/local/share/vim/vim70/plugin/getscriptPlugin.vim
      /usr/local/share/vim/vim70/plugin/gzip.vim
      /usr/local/share/vim/vim70/plugin/matchparen.vim
      /usr/local/share/vim/vim70/plugin/netrwPlugin.vim
      /usr/local/share/vim/vim70/plugin/rrhelper.vim
      /usr/local/share/vim/vim70/plugin/spellfile.vim
      /usr/local/share/vim/vim70/plugin/tarPlugin.vim
      /usr/local/share/vim/vim70/plugin/tohtml.vim
      /usr/local/share/vim/vim70/plugin/vimballPlugin.vim
      /usr/local/share/vim/vim70/plugin/zipPlugin.vim
      /home/mark/.gvimrc <<<<<<<<<<<<<<<<<
      /home/mark/.vim/after/color/tweak.vim
      ...


      I only source tweak.vim from .gvimrc and like you it's just a 'tweak' of
      the default colors. For some filetypes (ruby for eg) I have a
      ruby_cols.vim file in ~/after/ftplugin/ that contains specific hi
      commands:

      eg
      rubyBoolean, rubyComment, rubyDocumentation, rubyData,
      rubyStringDelimiter, rubyString, rubyNoInterpolation,
      rubyPseudoVariable, rubyInteger, rubyASCIICode, rubyFloat, rubyEscape,
      rubyInterpolation, rubyDataDirective, rubyOperator,


      which basically means I can go overboard tweaking ruby syntax ;-)


      cheers,


      --
      Mark
    • Show all 18 messages in this topic