On Tuesday, October 31, 2017 at 3:11:55 PM UTC+1, Christian Brabandt wrote: > It is true, that this can cause a problem. However, I am not sure its > correct to blame vim here.
> First, I think you need to configure your webserver to be able to view > dotfiles. I believe a default installation of at least apache won't let > you show dotfiles. Second, I wonder why those swapfiles are not deleted. > Somehow Vim must have crashed or be killed and in that case one > certainly don't want that the swapfiles are deleted (think of recovery). I agree. Although a multi-user system usually is connected via ssh - in that same scenario sometimes the connection is interrupted or people are on flaky wifi. This leaves ~ swapfiles littered over the system more frequently as a multi-user system over ssh. Which gives more reason to not litter the current directory for multi-user environments even with the argument of people editing the same file. Most people are annoyed by littered files over a filesystem. > One could argue, that swap files should be stored below ~/.vim directory > tree. But what if several users edit the same file? One also needs to > make sure, the path would be encoded into the name, but then we might > run into trouble with filename length limitations. A shared directory in /tmp for all vim instances on a multi-user system would solve the issue while not littering the filesystem. > So I think it in the users responsibility to configure Vim correctly > (check the directory option) to not have him litter his document root > with old swap files. Almost every .vimrc I've ever read had a line to set directory to exclude current directory and it is more an annoyance than a feature when countless people are asking this question over and over again what filename~ files are. I agree vim should be geared towards multi-user systems as well and warn when appropriate. It just makes more sense to have it in $TMP in that case and retain that behaviour. -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
