Ozaki Kiichi wrote:
> > Isn't this a bit too drastic? When termcap_active it should still be
> > possible to output text (e.g. from another timer command).
> > Also check msg_use_printf(). Looks like your change overrules its own
> > check for termcap_active.
> Hmm, yes. I think we should suppress updating screen while
> doing stoptermcap() ~ starttermcap() (i.e termcap_active == FALSE).
> Can we check termcap_active only in specific screen-updating functions
> (update_screen, or some), or should not do such?
Check the calls to screen_valid(). An explicit check at some of them
that termcap_active is FALSE should help.
We should perhaps also update must_redraw when bailing out.
It's needed when invoked from ex_redraw().
To the optimist, the glass is half full.
To the pessimist, the glass is half empty.
To the engineer, the glass is twice as big as it needs to be.
/// Bram Moolenaar -- b...@moolenaar.net -- 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
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.