Skip to content

Releases: jamessan/vim-gnupg

v2.7.1: vim-gnupg version 2.7.1

11 Nov 20:26
v2.7.1
6d106fa
Compare
Choose a tag to compare
  • Clear GPGOptions/GPGRecipients autocommands on BufUnload (#104)
  • Return early from Finish functions when buffer is not displayed

v2.7.0

10 Nov 03:43
v2.7.0
a72ab0b
Compare
Choose a tag to compare
  • Re-structure plugin so most of the implementation is under autoload/, with only required functionality in plugin/. Thanks to Lucas Hoffmann for the help. (#52)
  • Split the documentation into README (description, intro) and Vim help files (details relevant for usage). Thanks to Victor Koronen. (#13)
  • Honor 'verbose' to determine when to emit debug logs, as a gradual move away from g:GPGDebugLevel/g:GPGDebugLog
  • Do not use the '[/'] marks when saving the entire buffer to disk. This fixes an issue where plugins which reformat the buffer on save were causing only the reformatted portion of the buffer to be saved. (#96)

v2.6.1

15 Aug 13:49
v2.6.1
966808d
Compare
Choose a tag to compare
  • Preserve &readonly setting even if the file itself isn't read-only (e.g., using vim -R or :view)
  • Let Vim detect file encoding and file format when opening the file
  • Remove unnecessary (and potentially damaging) changing of &encoding when reading/writing the encrypted file
  • Avoid adding extra blank lines to buffer when loading unencrypted files
  • Set &buftype='acwrite' to ensure encrypted buffers are only saved via the plugin's BufWriteCmd (#77, #81, #86)
  • Add support for Gpg4win so the plugin can be used under cygwin (#62)
  • Better mimic Vim's behavior when using :saveas or :w newfile, and leave the original buffer modified
  • Improve handling of options and recipients buffers to avoid one triggering the other (#89)
  • Check for the standard armor header, rather than inspecting gpg's output to determine if a file is armored (#82)

v2.6

25 Apr 14:24
v2.6
541e333
Compare
Choose a tag to compare
  • Fix automatic setting of $GPG_TTY (#1)
  • Add g:GPGFilePattern to allow customizing which files are handled by the plugin (#4)
  • Restore prompting for recipients upon editing a new file. This had been dropped when refactoring to use the *Cmd autocmds. (#8)
  • Improved support for GPG 2.x
    • GPG agent will be used even if $GPG_AGENT_INFO isn't present, when GPG >= 2.1 is being used
    • Fallback to the gpg2 command if gpg isn't present
  • The User autocmd with pattern GnuPG is triggered upon successfully loading the buffer. This allows the user to define custom actions to be performed for vim-gnupg managed buffers. (#10)
  • Improve interaction with Windows command prompt when 'shellslash' is set. (#41)
  • Various bug fixes related to atypical configurations of GnuPG (#40, #50)
  • Detect when saving the file fails and do not mark the buffer as unmodified (#56)