On 11/03/2017 02:07 PM, Marvin Renich wrote: > * [email protected] <[email protected]> [171103 03:45]: >>> Another solution would be to always use the editing user's user:group >>> and perm 0600. >> I agree with this solution. And IMO the best way would be to create >> option for configure script+create option for vimrc configuration >> file, which can turn on/off this behavior (IMHO it's good to have >> option for users, who doesn't want this behavior). > I think having this behavior configurable is overkill and unnecessary in > practice. Can other users open original file, which has .swp file belonging to certain user:group with permissions 0600, as read-only with your solution? If not, it could be change of behavior, which can make some people unhappy -> that' why I thought it could be configurable behavior.
-- Zdenek Dohnal Associate Software Engineer Red Hat Czech - Brno TPB-C -- -- 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/d/optout.
signature.asc
Description: OpenPGP digital signature
