Loading ...
Sorry, an error occurred while loading the content.

Re: bug: swp recovery

Expand Messages
  • Bram Moolenaar
    ... [...] ... One machine is 32 bit, the other 64 bit. That is different enough for Vim not to be able to read the .swp file. For performance reasons Vim
    Message 1 of 2 , Nov 4, 2007
    • 0 Attachment
      Suresh Govindachar wrote:

      > Given below is information (uname -a, cat /proc/cpuinfo, vim
      > version) on two machines named crash_machine and recover_machine.
      >
      > Bug: On recover_machine, vim refuses to read a swp file created
      > on crash_machine.
      >
      > crash_machine>uname -a
      >
      > Linux 2.6.18-1.2257.fc5 #1 SMP Fri Dec 15 16:07:14 EST 2006 x86_64
      > x86_64 x86_64 GNU/Linux

      [...]

      > recover_machine>uname -a
      >
      > Linux 2.6.18-1.2869.fc6 #1 SMP Wed Dec 20 14:51:46 EST 2006 i686
      > i686 i386 GNU/Linux

      One machine is 32 bit, the other 64 bit. That is different enough for
      Vim not to be able to read the .swp file. For performance reasons Vim
      stores "int" and "long" values directly in the .swp file. Thus byte
      order and sizeof() matters.

      You might be able to compile a 32 bit Vim on the 64 bit machine and read
      the .swp files on both machines.

      --
      From "know your smileys":
      ;-0 Can't find shift key
      ,-9 Kann Umschalttaste nicht finden

      /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
      /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
      \\\ download, build and distribute -- http://www.A-A-P.org ///
      \\\ help me help AIDS victims -- http://ICCF-Holland.org ///

      --~--~---------~--~----~------------~-------~--~----~
      You received this message from the "vim_dev" maillist.
      For more information, visit http://www.vim.org/maillist.php
      -~----------~----~----~----~------~----~------~--~---
    Your message has been successfully submitted and would be delivered to recipients shortly.