On Thursday, August 8, 2013 12:39:20 PM UTC-5, Ben Fritz wrote: > On Thursday, August 8, 2013 12:25:07 PM UTC-5, Dahong Tang wrote: > > > > It's strange isn't it? You think nobody could mess with 644 files that > > belong to you, but if another user has write permission to the same > > directory, then he can overwrite your files using vim and totally mess them > > up. I don't understand why this was chosen as the default behavior of vim. > > Seems dangerous. > > When you do ":e yourfile | wq!" Vim is basically doing: > > $ cat yourfile > myfile > $ rm yourfile > $ mv myfile yourfile > > You're the one who gave others permission to mess with your filesystem.
Thanks for point that out. But it just seems like a strange behavior for a pure text editor. i.e., a dedicated text editor shouldn't change file permission and ownership of the files that it edits. I am sure many would disagree. -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
