Bug 205984 - GVim 7.0 randomly deletes lines
Summary: GVim 7.0 randomly deletes lines
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: vim
Version: 5
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-09-11 08:14 UTC by Mark Summerfield
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-09-03 11:46:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mark Summerfield 2006-09-11 08:14:54 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.6) Gecko/20060808 Fedora/1.5.0.6-2.fc5 Firefox/1.5.0.6 pango-text

Description of problem:
I cannot show you how to reproduce this problem.
I have some .hpp and .cpp files and in two of these files gvim
randomly deletes a line: the same one in each file. The lines bear
no relationship to one another. I think there is a bug in gvim 7.0s
undo/redo.

Version-Release number of selected component (if applicable):


How reproducible:
Sometimes


Steps to Reproduce:
1. Edit various .hpp and .cpp files
2. Sooner or later gvim will delete a random line.
3.

Actual Results:


Expected Results:


Additional info:
This is very aggravating.
I would switch back to gvim 6.4 but I don't know how to use yum to downgrade.

Comment 1 Mark Summerfield 2006-11-24 14:38:24 UTC
I have now changed to a new computer and so far the problem has not occurred,
although at the moment I'm not doing much C++ editing.
Also I'm now using Fedora Core 6 so perhaps that has a later version of Vim 7?

Comment 2 Karsten Hopp 2007-09-03 11:46:12 UTC
I think that was a temporary problem either in vim itself or in one of the
drawing libraries it relies on as I'm quite sure I would have gotten many
similar bugreports otherwise. Please repopen when you get that problem again
with a current version.


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