Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 116675

Summary: vim in gnome-terminal displays terminal control sequences
Product: [Fedora] Fedora Reporter: Alexandre Oliva <oliva>
Component: vimAssignee: Karsten Hopp <karsten>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
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-02-21 19:01:36 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 Alexandre Oliva 2004-02-24 10:42:48 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040217

Description of problem:
If you start vim within gnome-terminal, without arguments, the second
line will contain `^[34m' before the expected `~' character, as well
as in every `type :' line.  If you open a small file, the line below
the last line of the file will contain this same sequence.  If it's a
big file, the one-before-last line in the screen, will contain this
sequence as well.  I don't know whether this is a terminal emulation
bug in gnome-terminal/vte or an incorrect sequence issued by vim.

Version-Release number of selected component (if applicable):
vim-enhanced-6.2.253-2

How reproducible:
Always

Steps to Reproduce:
1.Start vim
2.Start vim small-file
3.Start vim big-file
    

Actual Results:  The `^[34m' sequence is displayed in all cases, as
described above.

Expected Results:  It shouldn't.

Additional info:

Comment 1 Karsten Hopp 2004-02-24 11:41:32 UTC

*** This bug has been marked as a duplicate of 115499 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:01:36 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.