Bug 1091495 - Default color scheme does not work well with rawhide gnome-terminal
Summary: Default color scheme does not work well with rawhide gnome-terminal
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: vim
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-25 18:02 UTC by Christophe Fergeau
Modified: 2015-09-23 00:22 UTC (History)
3 users (show)

Fixed In Version: 7.4.827-1.fc21
Clone Of:
Environment:
Last Closed: 2015-09-22 08:41:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Christophe Fergeau 2014-04-25 18:02:52 UTC
In rawhide, gnome-terminal defaults to a black gray background with white gray characters. 
vim color scheme does not work well by default in that setup (search highlights for example). :set background=dark must be used first. It would be great if gnome-terminal and vim could work well together without needing any tweaking.

Comment 1 Jaroslav Reznik 2015-03-03 15:44:16 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 2 Karsten Hopp 2015-09-22 08:41:44 UTC
This is supposed to be fixed in vim-7.4.827-1.fc21, please update your vim packages and reopen this bugzilla if the colors are still wrong with your terminal. 
 vim-7.4.827-1.fc21 is available in either the updates-testing repo or it got already moved to the update repo.

Comment 3 Karsten Hopp 2015-09-22 08:42:26 UTC
the f22 vim is already available in the updates repo: vim-7.4.827-1.fc22

Comment 4 Fedora Update System 2015-09-23 00:21:54 UTC
vim-7.4.827-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.