First up - "helpgrep \c" - thanks John, that's an awesome command I must remember! I had a bit of a look at the help, and got the impression that the information about samba was more about retaining user name ownership than permissions - see my notes on backupcopy above in response to Tony.
Thanks for your suggestions Ben - I tried them byt unfortunately they have no affect on the problem. I'm a little relieved that they don't too ;) - nor does it make sense to me that I'd have to disable all backups just to get vim to overwrite the existing file when saving - shouldn't those operations be orthogonal. For the record, I did also try starting vim with -u NONE to ensure it wasn't a setting I'd enabled, but the behaviour remained. I'm currently contemplating adding autocmds for BufWritePre and BufWritePost, to check if the file is accessible under cygwin, or via ssh to a linux server, and send the appropriate commands to get the file permissions before write, then restore them afterwards. I'll let update the thread with my results - though I'm still very open to simpler suggestions! -- You received this message from the "vim_use" 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
