Bug 141096 - /etc/gvimrc makes user gui colorscheme unreadable
Summary: /etc/gvimrc makes user gui colorscheme unreadable
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Other (show other bugs)
Version: Final
Hardware: Other SuSE Linux 10.0
: P5 - None : Normal
Target Milestone: ---
Assignee: Mads Martin Joergensen
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-29 06:30 UTC by Stuart Jansen
Modified: 2006-01-11 15:24 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stuart Jansen 2005-12-29 06:30:54 UTC
My .vimrc contains:
---
if has("gui_running")
  colorscheme desert
endif
---

Because of coloring rules in the /etc/gvimrc shipped with SUSE 10.0, files opened in gvim are completely unreadable. Vim reads system configuration files after reading user configuration files. The system configuration files should not contain anything that makes user preferred colorschemes unusable.

As a temporary workaround, I have converted my .vimrc to instead contain
---
if has("gui_running")
  autocmd GUIEnter * colorscheme desert " Work around SUSE bug.
endif
---
Comment 1 Mads Martin Joergensen 2006-01-04 08:17:51 UTC
Touching colorschemes and such is a very religious issue, and something we're
not going to address at this moment.

No matter what we do, someone will complain that the colors are horrible and
unreadable.
Comment 2 Stuart Jansen 2006-01-04 17:18:30 UTC
Question: did you try testing .vimrc containing only the configuration I mentioned? Did you honestly think that was acceptable?

Let me see if I understand the reasoning here: 1) If we leave things alone, gvim will be unusable for some of our users. They will reasonably complain and blame us. (This problem does not exist on RHEL, Gentoo, Fedora or Ubuntu.) 2) If we get rid of the rules so that the default is plain black text, it will be usable by all of our users. However, some relious fanatcis will complain. The choice is obvious, leave things the way they are?

Even if you're dead set on leaving this the way it is, mark as something that must be fixed for the 10.1 release.
Comment 3 Mads Martin Joergensen 2006-01-11 15:24:08 UTC
fixed.