vim leaving undeletable temporary files over CIFS

278 views

Skip to first unread message

Neil Bird

unread,

Oct 13, 2010, 9:53:25 AM10/13/10

to Vim Mailing List

I've been plagued for a while with hidden and undeletable files called
cifsXXXX (XXXX being some 4-char hex string) on my Windows XP box's share;
my only recourse to being rid of them is to reboot and then delete them.

I can't get anything but a filename from them, the file properties are
mostly blank (no security tab, e.g.). It's a share that I access from my
CentOS Linux box using CIFS and vim; the Linux side does show the files,
but says 'No such file' whenever they're accessed (until I reboot the
Windows box).

Anyway, I just did a reboot and thought to analyse the files this time.
They are binary files, all starting with "b0VIM 7.0", so I reckon they're
vim backup files. I don't know why they're not the usual .*.sw? format
(these do exist while editing).

I'm using the stick CentOS Vim of 7.0 (.109). Any ideas what's going on?

--
[neil@fnx ~]# rm -f .signature
[neil@fnx ~]# ls -l .signature
ls: .signature: No such file or directory
[neil@fnx ~]# exit

Christian Brabandt

unread,

Oct 13, 2010, 11:30:32 AM10/13/10

to vim...@googlegroups.com

On Wed, October 13, 2010 3:53 pm, Neil Bird wrote:
>
> I've been plagued for a while with hidden and undeletable files called
> cifsXXXX (XXXX being some 4-char hex string) on my Windows XP box's share;
> my only recourse to being rid of them is to reboot and then delete them.
>
> I can't get anything but a filename from them, the file properties are
> mostly blank (no security tab, e.g.). It's a share that I access from my
> CentOS Linux box using CIFS and vim; the Linux side does show the files,
> but says 'No such file' whenever they're accessed (until I reboot the
> Windows box).
>
>
> Anyway, I just did a reboot and thought to analyse the files this time.
> They are binary files, all starting with "b0VIM 7.0", so I reckon they're
> vim backup files. I don't know why they're not the usual .*.sw? format
> (these do exist while editing).
>
>
> I'm using the stick CentOS Vim of 7.0 (.109). Any ideas what's going
> on?

I think, this issue has been solved with Vim 7.3. At least there used to
be an entry in the todo list, mentioning this behaviour and now I can't
find it. So you might need to try a newer Vim version.