vim/vim-gnupg
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Ensure buftype=acwrite is always set for the buffer

Browse Source 
The user may be a) editing an existing encrypted file, b) creating a new
encrypted file, c) editing an unnamed buffer and saving it as an
encrypted file.  In all cases, 'buftype' should be set correctly once we
know the buffer is intended to be encrypted.

Signed-off-by: James McCoy <jamessan@jamessan.com>
This commit is contained in:
James McCoy 2017-10-22 23:16:28 -04:00
parent e7b6648ab2
commit ae1b31965e
No known key found for this signature in database
GPG Key ID: DFE691AE331BA3DB
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
plugin/gnupg.vim
View File

@ -1,5 +1,5 @@
" Name: gnupg.vim
" Last Change: 2017 May 31
" Last Change: 2017 Oct 22
" Maintainer: James McCoy <jamessan@jamessan.com>
" Original Author: Markus Braun <markus.braun@krawel.de>
" Summary: Vim plugin for transparent editing of gpg encrypted files.
@ -478,6 +478,8 @@ function s:GPGDecrypt(bufread)
silent execute ':doautocmd BufNewFile ' . fnameescape(autocmd_filename)
call s:GPGDebug(2, 'called BufNewFile autocommand for ' . autocmd_filename)
set buftype=acwrite
" This is a new file, so force the user to edit the recipient list if
" they open a new file and public keys are preferred
if (g:GPGPreferSymmetric == 0)
@ -752,6 +754,7 @@ function s:GPGEncrypt()
if auType == 'BufWrite'
setl nomodified
setl buftype=acwrite
let &readonly = filereadable(filename) && filewritable(filename) == 0
endif