Derek Wyatt wrote: > > The funny thing: > > - open a file, that is not used by other processes > > - saving changes work > > - open the same file with another process > > - gvim detects this and complains on save, that it is a read only > > file* > > - the other process stops using the file > > - the "weird" part: gvim still refuses to save changes to the > > file, even if now there is no reason for that > > Why isn't there a reason for it? If you wrote the file in process 1 > then your buffer in process 2 is stale, and if you now write the file > from process 2 you blow away the changes you made in the process 1. > It's readonly for a reason.
No. After file change by process 1, gvim (process 2) asks "File has changed, do you want to load latest version" (or similar). Then I do that (click YES), load the latest file content. Then I do more changes (in gvim, process 2). And want to save them. And it refuses. There is no stale data, no data that would be lost. But gvim still refuses to write. If there were new data on file, not loaded by gvim, then your logic would apply and make sense. But the problem scenario is different. Regards, David --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
