On Tuesday, June 11, 2013 4:56:08 PM UTC-5, John Wiersba wrote: > > I run into several issues when editing/viewing files on a filesystem with > 64-bit inodes on vim 7.3 (built from source) on AIX 6.1. I > didn't see any mention of similar issues in the patches list. Have I missed > something? > > Some of the issues: > $ cd filesystem_with_64_bit_inodes > $ vim -u NONE file1 file2 > :n # stays in file1 instead of advancing to file2 > :e file3 # stays in file1 instead of editing to file3 >
Does Vim give you any messages when you try to edit the next file? In particular, does it mention unsaved changes? By default, Vim will not let you "abandon" a buffer with unsaved changes. If this is your problem, you can: 1. Save your changes before opening a new buffer 2. Open the new buffer in a split window or tab page instead of the current window with :split, :new, :tabe, :tabnew, etc. 3. set the 'hidden' option so Vim will let you keep your buffers unsaved even if they are not visible anywhere 4. set the 'confirm' option so Vim asks you what to do when you try to abandon unsaved buffers 5. use :e!, :n!, etc. to abandon your changes and go to the next file anyway -- -- 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.
