Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 230064 - vim does not handle double byte characters properly
Summary: vim does not handle double byte characters properly
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: vim
Version: 4.0
Hardware: i386
OS: Linux
Target Milestone: ---
: ---
Assignee: Karsten Hopp
QA Contact: Kevin Baker
Depends On:
TreeView+ depends on / blocked
Reported: 2007-02-26 12:59 UTC by Douglas Held
Modified: 2014-12-01 23:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-05-13 09:48:57 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Douglas Held 2007-02-26 12:59:57 UTC
Description of problem:
Double byte characters are not handled correctly in vim

Version-Release number of selected component (if applicable):
[doug@rhe4 Test]$ rpm -qa | grep vim

How reproducible:
1. Attach to RHE server with Putty 0.58 from Windows XP SP2
2. in default bash shell, create a new text file (e.g. vi test )
3. insert the following text: "before£after"
   (Inserting the £ as Shift-3 on the UK keyboard)
4. The text displays as "before£after"
5. Type Esc and :w to save the file
6. The cursor is now on the "e" in "after"
7. Type LArrow eleven times... the cursor will be at the beginning of the line
8. Type RArrow 7 times.  The cursor will be on the £ symbol
9. Type right arrow one more time.  The "£" symbol changes to an "a".
10. The text stays corrupted on the screen and can no longer be edited reliably.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Douglas Held 2007-02-26 13:05:20 UTC
How reproducable: always

Expected results: the characters on screen should not change when vi is not in
editing mode.

Additional info: TERM environment variable can be set to either "vt100" or
"xterm" to obtain these results.

Comment 3 Phil Knirsch 2011-05-13 09:48:57 UTC
This request was evaluated by Red Hat Engineering for inclusion in a Red
Hat Enterprise Linux maintenance release.

Red Hat does not currently plan to provide this change in a Red Hat Enterprise
Linux update release for currently deployed products.

With the goal of minimizing risk of change for deployed systems, and in
response to customer and partner requirements, Red Hat takes a conservative
approach when evaluating enhancements for inclusion in maintenance updates
for currently deployed products. The primary objectives of update releases
are to enable new hardware platform support and to resolve critical

However, Red Hat will further review this request for potential inclusion
in future major releases of Red Hat Enterprise Linux.

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