I used -u NONE so that my configuration would be as simple as possible. I normally use a custom .vimrc which does not have compatible mode set.
This buggy behavior happens only on AIX 6.1 with filesystems which have 64-bit inodes. It does not happen on other filesystems or other operating systems (Linux, SunOS). The files in my example have not been changed. It has something to do with vim not being able to read 64-bit inodes (such as with a readdir() vs readdir64() system call). When I use vim -u NONE a b, the status line says "a" 1 line, 10 characters. After :n, the status line briefly says :n (as I type it) and then returns to saying "a" 1 line, 10 characters. The file contents still are the contents of file a. After the next :n, the status line briefly says :n (as I type it) and then says E165: Cannot go beyond last file. So, vim knows I have another file in my list, but somehow cannot show it. And then it knows I've reached the end of the file list. Vim behaves normally on AIX 6.1 if my current directory (where file a and b are located) is on a different filesystem. For further information, there are other utilities that have problems with this same 64-bit inode filesystem, such as chmod -R, chown -R, make and cd from an sftp client after the sftp server process has cd'ed to this filesystem. These system utility bugs all have to do with utilities not being built with readdir64() and I have an open PMR with IBM to fix those. Other system utilities such as ls -R and find work properly. However, this is a copy of vim that I built myself. So somehow the normal build of vim on AIX 6.1 does not function properly when confronted with a 64-bit inode filesystem. When I use a hand-built vim 7.3 from other OSes (SunOS 5.10 or RHEL 5.5) to access the same filesystem, I do *not* experience this problem (vim behaves normally as I expect). So the problem is for AIX 6.1 only and only for a 64-bit filesystem. >________________________________ > From: Ben Fritz <[email protected]> >To: [email protected] >Cc: "[email protected]" <[email protected]>; John Wiersba <[email protected]> >Sent: Tuesday, June 11, 2013 10:19 PM >Subject: Re: Vim 7.3 bug on AIX 6.1 with 64-bit inodes > > >On Tuesday, June 11, 2013 4:56:08 PM UTC-5, John Wiersba wrote: >> --- Options --- >> ... >> compatible key= shellcmdflag=-c ttytype=xterm > >I note you have 'compatible' set. Vim behaves much nicer with 'nocompatible', >but I doubt this is your issue. You might give it a shot anyway. Just creating >a .vimrc should be enough to force 'nocompatible', or you can launch Vim with >the -N flag. > >-- >-- >You received this message from the "vim_dev" maillist. >Do not top-post! Type your reply below the text you are replying to. >For more information, visit http://www.vim.org/maillist.php > >--- >You received this message because you are subscribed to the Google Groups >"vim_dev" group. >To unsubscribe from this group and stop receiving emails from it, send an >email to [email protected]. >For more options, visit https://groups.google.com/groups/opt_out. > > > > -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
