> None of the above disagrees with what I said. I apologize if I gave you a reason to think so. I was just trying to point out is not quite correct actions by vim which running with root privileges.
> You also don't show whether the undo files after steps 4 and 5 > > are the same inode. It may not be a matter of vim changing the > > ownership of the existing undo file, but creating a new file. $ sudo ls -lai /root/.vim/undofiles/%var%www%vesperaudio.com%robots.txt 391067 -rw-r----- 1 root www-data 519 Sep 7 15:43 /root/.vim/undofiles/%var%www%vesperaudio.com%robots.txt $ sudo chown cac2s.cac2s /root/.vim/undofiles/%var%www%vesperaudio.com%robots.txt $ sudo vim /var/www/vesperaudio.com/robots.txt made some changes an ":wq" $ sudo ls -lai /root/.vim/undofiles/%var%www%vesperaudio.com%robots.txt 391067 -rw-r----- 1 root www-data 519 Sep 7 15:51 /root/.vim/undofiles/%var%www%vesperaudio.com%robots.txt the inode of the undo file is not changed > > so maybe correctly set the owner of undo file the same as that of the > > > file being edited, knowing that vim running as root, which guarantees > > > the continued use of the file changes for an undo/redo actions? > > > > Which only works for root, as I stated before. Non-root users can't set > > arbitrary users as the owner for their files, so you still have a > > situation where it's not possible to make the owner of the undo file > > match that of the file being edited. that's why I said about the need to verify that vim running as root: > ... knowing that vim running as root... -- -- You received this message from the "vim_dev" 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_dev" 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.
