vim-gnupg

History

James McCoy 7d0a149169 Remove GPGCleanup function If 'autowrite' is set, an encrypted buffer is modified, and ":q!"/"ZQ" is executed, GPGCleanup's "only!" would cause the buffer to be abandoned. Due to 'autowrite' and the VimLeave autocmd not using "nested", abandoning the buffer causes Vim to write the buffer, which is currently unencrypted, overwriting the encrypted file with plain text. Since the user can more reliably clear their own console/terminal scroll back than we can, simply remove this functionality. It's safer than trying to unwind the twisty passages of Vim's autocmds, especially those of the *WriteCmd variety. Closes jamessan/vim-gnupg#77 Signed-off-by: James McCoy <jamessan@jamessan.com>	2017-02-14 22:11:52 -05:00
..
gnupg.vim	Remove GPGCleanup function	2017-02-14 22:11:52 -05:00

If 'autowrite' is set, an encrypted buffer is modified, and ":q!"/"ZQ"
is executed, GPGCleanup's "only!" would cause the buffer to be
abandoned.  Due to 'autowrite' and the VimLeave autocmd not using
"nested", abandoning the buffer causes Vim to write the buffer, which is
currently unencrypted, overwriting the encrypted file with plain text.

Since the user can more reliably clear their own console/terminal scroll
back than we can, simply remove this functionality.  It's safer than
trying to unwind the twisty passages of Vim's autocmds, especially those
of the *WriteCmd variety.

Closes jamessan/vim-gnupg#77
Signed-off-by: James McCoy <jamessan@jamessan.com>

2017-02-14 22:11:52 -05:00

gnupg.vim

Remove GPGCleanup function

2017-02-14 22:11:52 -05:00