在 2013年10月18日星期五UTC+8上午12时10分12秒，Ben Fritz写道： > On Thursday, October 17, 2013 10:08:19 AM UTC-5, Yggdroot Chen wrote: > > > 在 2013年10月17日星期四UTC+8下午9时54分53秒，Ben Fritz写道： > > > > The issue is you're trying to prevent the user from rescuing their Vim > > > from a misbehaving command. You are trying to potentially cause data loss > > > when they need to force-kill their Vim instead of just stopping a single > > > bad command. > > > > Don't do that. > > > > > > what I want is to prevent ctrl-c from interrupting my program. But there > > exist this issue. > > > > WHY do you want to do this?
well，I am writing a vim plugin that need to get input from user, and I want to define the behavior of ctrl-c. if there is no try-except in while loop, annoying message will be reported as the attachment shows. I want to recover some options after ctrl-c is pressed using vim.command(). Anyway, I think this issue is a critical bug. -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
<<attachment: 未命名.jpg>>
