*BSD News Article 46982


Return to BSD News archive

#! rnews 2175 sserve.cc.adfa.oz.au
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!newshost.marcam.com!zip.eecs.umich.edu!newsxfer.itd.umich.edu!agate!tcsi.tcs.com!uunet!in1.uu.net!mozz.unh.edu!toto.plymouth.edu!oz.plymouth.edu!not-for-mail
From: ted@oz.plymouth.edu (Ted Wisniewski)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: 2.0.5R: vim-3.0 anyone?
Date: 16 Jul 1995 13:18:41 -0400
Organization: Plymouth State College - Plymouth, NH.
Lines: 35
Message-ID: <3ubhlh$d27@oz.plymouth.edu>
References: <95Jul14.213710.5319@ne.snafu.de> <3u7d8p$bdi@agate.berkeley.edu> <3u882m$afk@bell.maths.tcd.ie>
NNTP-Posting-Host: oz.plymouth.edu

In article <3u882m$afk@bell.maths.tcd.ie> creilly@maths.tcd.ie (Colman Reilly) writes:
>jkh@violet.berkeley.edu (Jordan K. Hubbard) writes:
>
>>In article <95Jul14.213710.5319@ne.snafu.de>,
>>Nora E. Etukudo <nora@ne.Snafu.DE> wrote:
>>>I've mysterious errors  on working with 'vim-3.0'  (vi-clone). If I switch
>>>to any of the "Insert-Modes", I get an error message like this
>>>
>>>    `Seek error in swap file read'
>
>>That is very strange!  I've forwarded your message to the VM system hackers
>>in the chance that they'll be able to divine some clues from it.
>
>Actually, what happens is that vim uses a sort of swap file itself, in which it stores what is basically a complete history of your editing session, so it's
>an internal Vim error. I looked at it briefly, but I haven't had a chance to 
>really spend time with it yet. I don't get any errors when I compile it.

	Actually, it may not be internal to VIM,  I had a similar problem
with Harvest 1.2;  It seems to be a "type" problem.  I wrote an interface
to lseek that solved the problem (It was strange to have to do it that way).

Here is "mylseek", it returns a "long" instead of "off_t";  I cooerce the
type back to "off_t" in the calling procedure.  I hope this helps in trouble
shooting the problem,  I have heard that the problem persists in 2.0.5.

long my_lseek(fd, offset, whence)
int fd;
long offset;
int whence;
{
        off_t lseek(int, off_t, int);

        return((long) lseek(fd, (off_t) offset, whence));
}