On Thu, Jun 9, 2016 at 2:56 PM, Charles E Campbell < drc...@campbellfamily.biz> wrote: > if libraries are used, the system may update the library (while one > is on holiday), potentially rendering encrypted text unreadable. I know > that these things should be done in a backwards compatible fashion, but > Murphy's Law plus having many users guarantees trouble will happen. > > I agree that libraries will get better testing, though. >
Good point. So we should be sure to link statically to the library. Of course if the system updates to a new Vim we could still have the problem. It sounds like once the encryption is finished we should add a reference version encrypted file to the tests, and test that vim can decrypt it. Then the test will fail if a library update breaks the decryption. -- -- 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.
