Tony Mechelynck <[EMAIL PROTECTED]> writes: > On 24/11/08 08:42, anhnmncb wrote: >> Tony Mechelynck<[EMAIL PROTECTED]> writes: >> >>> On 24/11/08 05:32, anhnmncb wrote: >>>> Yes, I still want to have a function that can let me confirm when quiting >>>> even all >>>> buffers have saved. >>>> >>>> Actually, I want map it to a key, so when I'm away, I can call it to >>>> prevent someone from closing my gvim by accident. >>>> >>>> I know mksession is a better solution, but I still want a function like >>>> that :) >>> hm, can't you lock your screensaver (or something) so that when you've >>> been away, you must type your password before you can use the computer? >>> Then other people could do nothing "by accident", except of course pull >>> the AC plug from the wall, but I guess you can't forbid that (except >>> maybe by locking the door to the room with your computer). ;-) >> >> Haha~ But I want other people can use my computer, just not let them >> touch my gvim :) >> >>> >> > > Hm, then I think you have a problem. > > Maybe you should create distinct usernames (login names) so that each > user won't clobber the others' work. But I suppose you'll tell me that > that isn't what you want either.
right, I know this way, but not what I want either :) > > > Best regards, > Tony. -- Regards, anhnmncb gpg key: 44A31344 --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
