Bug 166737
Summary: | RHEL3: odd shape cursor in emacs when background is not white | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Boris Vinarsky <borisv> |
Component: | emacs | Assignee: | Chip Coldwell <coldwell> |
Status: | CLOSED WONTFIX | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-19 18:55:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Boris Vinarsky
2005-08-25 02:45:45 UTC
Does this still happen with RHEL3 U6 ? What did you upgrade from? (emacs-21.2 hasn't I can't reproduce this on RHEL4 or Fedora Core. Sorry about the incomplete sentence. That should say: "(emacs-21.2 hasn't shipped in RHEL3.)" I used a system that was installed from original CDs I received from Dell along with the system. I did not use any external source for emacs. Today I have upgraded a system to everything latest: [root@chico root]# cat /etc/redhat-release Red Hat Enterprise Linux WS release 3 (Taroon Update 6) Currently on that system: [root@chico root]# rpm -q emacs emacs-21.3-4.7 I tested emacs with not-white backgroup. The issue is still there, no changes. This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |