aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/contrib/vim (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Simplify filename matching in redact_pass.vimTom Ryder2018-06-242-40/+11
| | | | | Use the autocmd pattern to match the password filename rather than doing it manually within the called function.
* Replace noplaintext.vim as redact_pass.vim pluginTom Ryder2018-06-103-46/+121
| | | | | | | | | | | | | | | | | | | | | | | | | | | Per debugging from Enno Nagel <enno.nagel+vim@gmail.com>, it's become apparent to me that to have any degree of confidence that none of these options have actually got any plaintext password data in them, we need to disable the options globally when a password file is edited. In particular, in the case of the 'viminfo' global option, it's not possible to disable it per path, and not terribly meaningful either; things like the last seach pattern or the contents of registers, i.e. global state of the editor, are recorded. There's no sensible approach I can see except to actually switch the feature off entirely by blanking it. I've therefore completely rewritten this, to make as thorough a check as possible that the Vim user is editing a pass(1) file by calling `pass edit`, and then to disable the "leaky" options globally, with an explicit warning so that the user can see it's been done. This plugin is also available as Vim script #5707: <https://www.vim.org/scripts/script.php?script_id=5707> Its homepage is here: <https://sanctum.geek.nz/cgit/vim-redact-pass.git/about/>
* Add tejr's scriptJason A. Donenfeld2015-01-151-0/+46