Marc Weber wrote: > Wired things which I think can happen: > 1) run a viml loop > 2) resize the window > > while viml is in a loop it calls line_breakcheck which in turn calls > ui_breakcheck which calls gui_mch_update which can recieve resize events > which can trigger an au command which can disturb your initial loop ? > > I would not expect vim calling any additional viml while I run :while > true | let dummy=1 | endwhile > > I have no proof yet. Its just something which I think could happen likely. > > Anyway. why doesn't Vim just listen to SIGINT, why does it use > line_breakcheck instead to get notified if the user wants to interrupt viml > code?
What would happen on SIGINT, exit Vim? No, there has to be a very controlled way to break out of whatever is currently being done. This does not always mean returning to the main loop. C does not have exceptions. If you have a specific problem, please report it with a reproducible example. -- hundred-and-one symptoms of being an internet addict: 79. All of your most erotic dreams have a scrollbar at the right side. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
