On 24/11/08 13:37, Ben Schmidt wrote: > Tony Mechelynck wrote: >> On 24/11/08 10:57, anhnmncb wrote: >>> Tony Mechelynck<[EMAIL PROTECTED]> writes: >>> >>>> On 24/11/08 08:44, anhnmncb wrote: >>>>> Tony Mechelynck<[EMAIL PROTECTED]> writes: >>>>> >>>>>> On 24/11/08 04:52, anhnmncb wrote: >>>>>>> As title, and I don't think it's very useful when editing a directory. >>>>>> When editing a directory, the netrw plugin uses ":setlocal noswapfile", >>>>>> so you don't need to do anything, the swapfile is already disabled on >>>>>> that directory. >>>>> Why I still find that vim produces a _.swp file in dir that editing? >>>> I don't -- while editing my home directory, "ls -l ~/.sw*" does list >>>> four files, but the most recent of them dates from more than a month ago. >>>> >>>> You might create a swapfile (with no filename in its name) when you edit >>>> a [No Name] file; then that swapfile will remain if Vim crashes or gets >>>> killed. >>> Here generates _.swo and _.swp, I'm sure the dir hasn't these files >>> before I edit it. >>> >>> btw. my gvim version is official 7.2 for windows. >>> >> Mine is 7.2.049 for Linux (compiled from official sources, official >> patches 1-49, and one unofficial patch which is about floating point >> functions), Huge version with GTK2/Gnome GUI, Perl, Python, Ruby and TCL >> but not MzScheme, etc. etc. etc. >> >> I suppose that the fact that mine generates .swp, .swo, etc., rather >> than _.swp, _.swo, etc. for [No Name] files is due to the fact that I'm >> on Linux and you're on Windows. >> >> Are you sure you aren't currently editing a [No Name] buffer (possibly >> as a hidden buffer, if you have 'hidden' set)? The ":ls!" command might >> help you. Look for buffers with a (active) or h (hidden) left of their name. > > You can find out what those swap files are by navigating to that > directory in cmd and doing > > vim -r > > to get a list (not all that helpful) or
well, at least it will tell you the name of the buffer to which this swapfile applies. > > vim -r _.swp > > which will try to 'recover' the specific file, showing you what's in it. > If indeed it is a directory listing, something must be different or > broken with netrw or Vim on windows. If it's something else, well, > you'll find out what it is and can decide for yourself what to do. > > An alternative to going via cmd is to navigate in Vim to the directory, > via :cd and then do > > :recover _.swp > > Ben. Best regards, Tony. -- Whatever became of eternal truth? --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
