thomas wrote:
>> but note that you can always get into the :debug mode
>
> I have to admit I didn't think of that. This could even be scripted
> with :debugg. Interesting.
>
> Another not so conventient and more traditional solution would be to
> protect many passwords with one master password user have to enter
> every time a password is used.
>
> In a slightly more advanced version this user-defined password could
> be retained for a while so that you have to enter it only once when
> loading/saving many files. But then, since vim doesn't have timer
> events this would rely on cursorhold or similar. And a password is
> only as strong as the password that's used to protect it.
>
> thomas.
Vim can store the current time -- see ":help reltime()". Store it when the
user types in the master password, compare it with the time when a password is
needed, and ask the master password again if the time interval is "too long".
But you would have to store, not necessarily the master password itself, but
at least something (a hash key?) which would allow you to recognise it.
Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
160. You get in the elevator and double-click the button for the floor
you want.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
