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.


Best regards,
Tony.
-- 
You know you have a small apartment when Rice Krispies echo.
                -- S. Rickly Christian

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to