Upstream believes it is not a bug. The proper way to disable the use of .viminfo is to ":set viminfo=".
I pointed out that symlinking to /dev/null is a fairly common idiom; but OTOH there would be a strong case that the idiom applies to files that the user supplies to a program; .viminfo is something that vim generates itself, and overwrites each time (moving a temporary file over it), so replacing it with a symlink could be considered "mucking with internal vim stuff". See Bram's assessment, here: http://tech.groups.yahoo.com/group/vimdev/message/46903 ** Changed in: vim (Ubuntu) Status: Confirmed => Rejected -- .viminfo file gets deleted and re-created with 666 permissions https://bugs.launchpad.net/bugs/78960 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
