John wrote:
> The only changes that would appear relevant to me would be
> changes to samba configuration files - but the sys admins
> have so far said "Well if it works in notepad, and it works
> in wordpad - it's vim that's broken, not the samba config" -
> and as yet, I don't know enough to argue.
The change you want is in the Samba "create mask" config.
Google following for info:
"create mask" samba
Try creating a file with something simple like this at command
prompt (where x: is a mapped drive letter):
echo Hello world > x:hello.txt
The Linux permissions on hello.txt should be what "create mask"
specify.
Notepad replaces an existing file by overwriting it. That is
what simple (and stupid) programs do. More sophisticated
programs like Microsoft Word write to a temporary file, then
rename the files after the write has successfully completed.
That way, a power failure or network breakage will at least
leave the original file intact (whereas Notepad would leave you
with a corrupted file).
I mentioned Word because that is where people most often see the
issue. They find that saving a file in Word changes the NTFS
permissions on the file (that depends on the file permissions on
the directory), whereas saving a file in Notepad does not.
John
--
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
