Bug 116675 - vim in gnome-terminal displays terminal control sequences
vim in gnome-terminal displays terminal control sequences
Status: CLOSED DUPLICATE of bug 115499
Product: Fedora
Classification: Fedora
Component: vim (Show other bugs)
rawhide
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Karsten Hopp
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-02-24 05:42 EST by Alexandre Oliva
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 14:01:36 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Alexandre Oliva 2004-02-24 05:42:48 EST
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 06:41:32 EST

*** This bug has been marked as a duplicate of 115499 ***
Comment 2 Red Hat Bugzilla 2006-02-21 14:01:36 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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