Bug 187192
Summary: | VIM editor leaves remnants on scroll with :set noruler on Gnome Terminal | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Khoa Ton <khoa> |
Component: | vte | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | khoa, neil |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-05-10 18:55:03 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
Khoa Ton
2006-03-29 03:02:19 UTC
This problem is affecting users of /bin/vi (namely root user) since /bin/vi is /usr/bin/vim without potential security issues, and specifically without ability to turn ":set ruler" on. Workaround is for the root user to use /usr/bin/vim and ":set ruler", negating the security features of /bin/vi, if Gnome Terminal is used. I tried the following: # TERM=gnome /bin/vi /etc/passwd and the problem of text remnants on scroll still existed. However, the following setting: # TERM=ansi /bin/vi /etc/passwd eliminated the text remnants on scroll problem! So, based on this last piece of information: 1) Gnome Teminal does seem to be exhibiting bug on redraw, since even setting TERM=gnome exhibited this issue with vim. 2) The workaround to use /bin/vi (secure version of /usr/bin/vim) as root would be something like: # alias vi="vi -T ansi" This would be safer than aliasing root's vi to /usr/bin/vim to bypass the redraw problem. Might this then be an issue with the gnome-terminal termcap entries? Does running TERM=gnome from within an xterm exhibit the problem? What about TERM=xterm within gnome-terminal? [wrt. your above tests, were they both run under gnome-terminal?] (In reply to comment #3) > Might this then be an issue with the gnome-terminal termcap entries? > > Does running TERM=gnome from within an xterm exhibit the problem? What about > TERM=xterm within gnome-terminal? > > [wrt. your above tests, were they both run under gnome-terminal?] Yes, all above tests were done within Gnome Terminal 2.14.0 unless specifically stated otherwise. Following are the tests as per your request: Command: TERM=$TERM /usr/bin/vim -U NONE -u NONE /etc/passwd and: /usr/bin/vim -T $TERM -U NONE -u NONE /etc/passwd Terminal program tested Gnome Terminal xterm TERM=ansi good good TERM=gnome BUG good TERM=xterm BUG good Doesn't look like an issue with termcap entries. The recent update to vte (vte-0.12.1-1.fc5.1) seems to have fixed this. Updated to vte-0.12.1-1.fc5.1 as suggested and the problem went away after a reboot (maybe just restarting Gnome would have been sufficient). I'll leave this bug request as NEW since I don't know the protocol for closing/duplicate, etc... Seems like this bug should be filed under VTE and closed? Thanks Ron! Thanks guys, closing. |