Hi,
Here are two patches about blowfish2 document.
1. Blowfish2 was introduced with 7.4.399 and fixed with 7.4.401, and it is newer
than 7.4.237. I think using has('patch-7.4.401') is simpler:
--- a/runtime/doc/editing.txt
+++ b/runtime/doc/editing.txt
@@ -1467,7 +1467,7 @@ Thus the condition failing doesn't mean
test for blowfish with: >
v:version >= 703
And for blowfish2 with: >
- v:version > 704 || (v:version == 704 && has('patch401'))
+ has('patch-7.4.401')
<
*E817* *E818* *E819* *E820*
When encryption does not work properly, you would be able to write your text
(Do we need to care who applies the patch 7.4.401 and doesn't apply 7.4.237?)
2. The patch level written in options.txt is different from editing.txt:
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -2302,7 +2302,7 @@ A jump table for the options with a shor
the encrypted bytes will be different.
*blowfish2*
blowfish2 Blowfish method. Medium strong encryption. Requires
- Vim 7.4.399 or later, files can NOT be read by Vim 7.3
+ Vim 7.4.401 or later, files can NOT be read by Vim 7.3
and older. This adds a "seed" to the file, every time
you write the file the encrypted bytes will be
different. The whole undo file is encrypted, not just
Regards,
Ken Takata
--
--
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.
