Currently, my template script creates a temporary .vimrc invoked with -u that sets viminfo= to nothing so viminfo doesn't get saved/used. I was doing the same with the swap file so no swap is created in this instance. The BufWriteCmd very well may fit the bill.
The goal is to make this user friendly so people can use it who have only the most rudimentary of 'vi' knowledge and I think BufWriteCmd will fit the bill in this particular case, assuming that 'gpg' can handle being passed the data as it does in a standard pipe as in from the CLI.
As far as :w !cmd not encrypting the text, this isn't too big of a deal so long as it's not written to disk. Nothing will withstand someone who has access to read directly from memory and if it gets to that point, I have much bigger issues on hand.
--
You received this message from the "vim_use" 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
--
Molon Labe
"Come and take them"
"By divine design, fathers are to preside over their families in love and righteousness and are responsible to provide the necessities of life and protection for their families."
"The Marines I have seen around the world have the cleanest bodies, the filthiest minds, the highest morale, and the lowest morals of any group of animals I have ever seen. Thank God for the United States Marine Corps!" -Eleanor Roosevelt