[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: strange vim startup/loading error



 

> -----Original Message-----
> From: Karsten Hopp
> 
> On Fri, Apr 21, 2006 at 11:42:28AM -0400, Marc Wiatrowski wrote:
> > I recently upgraded a box from RHEL 3 to 4 and I'm now getting
> > the following error with vim when I edit one specific file.  All
> > other files seem to work without this error. 
> > 
> > E295: Read error in swap file
> > E316: ml_get: cannot find line 1
> > Hit ENTER or type command to continue
> > 
> > Everything seems to work fine on that file after I hit enter.  Its
> > just getting annoying mostly.
> > 
> > If I vi the same file on a box still running RHEL 3, I don't get
> > the error.  Both the RHEL 3 & 4 boxes are using vim 6.3 but 
> different
> > patch levels 6.3.81 (RH 6.3.046-0.30E.4) vs 6.3.82 (RH 
> 6.3.046-0.40E.7)
> > 
> > I also tried compiling my own current 6.4 version from 
> source and then
> > even the 7.0e beta on the RHEL 4 box and still get the 
> error.  Just for
> > kicks though I then compiled the 7.0e beta on the RHEL 3 box and I 
> > do not get the error!
> > 
> > I've tried renaming the file, creating a new file... same error.
> > 
> > Tried googling those errors but mostly just get the vim source code.
> > I can't really give out code for the file I am trying to 
> edit either.
> > 
> 
> Is there an old vim swap file from an previous editing attempt ? 
> Try 'ls -l .*swp' in that directory and rename/remove that 
> file if you're sure
> that you don't have this file opened in another vim.
> 

Sorry, should have thrown this relative bit in.  I had tried
':sw' while editing the file.  The swap file is there while I'm
running vim, but its gone when I close the file.  So I'm assuming
that since its gone there isn't any left over corrupt-ness next
time I edit it. 

It's the same mounted directory on both machines (off a 3rd file server)
and I can create and edit other new or old files in that same directory
from both machines which out a problem.

thanks,
marc



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]