Bug 205984

Summary:	GVim 7.0 randomly deletes lines
Product:	[Fedora] Fedora	Reporter:	Mark Summerfield <mark>
Component:	vim	Assignee:	Karsten Hopp <karsten>
Status:	CLOSED NOTABUG	QA Contact:	David Lawrence <dkl>
Severity:	high	Docs Contact:
Priority:	medium
Version:	5
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:	2007-09-03 11:46:12 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 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.