On Sunday, August 10, 2014 3:41:38 PM UTC-7, Bram Moolenaar wrote:
> Jacob Niehus wrote:
>
>
>
> > I narrowed it down to the point I can reproduce it with no
>
> > configuration file. Apparently keys typed while a shell command is
>
> > executing are drawn on screen immediately, then drawn again after the
>
> > command finishes. Also I should have mentioned before that this is not
>
> > Cygwin-specific; it just was more apparent on Cygwin because Cygwin is
>
> > slow, relatively speaking.
>
> >
>
> > vim -u NONE -i NONE -c 'autocmd InsertCharPre * call system("sleep 1")'
>
>
>
> Sounds like echo is on while executing the system command, but the typed
>
> character is not consumed by the external command.
>
>
>
> Switching echo off may have undesired side effects, e.g. for a command
>
> that asks for confirmation.
>
>
>
> Perhaps we could detect we get a key right after system() and redraw.
>
> That will cause flicker though.
>
>
>
> --
>
> hundred-and-one symptoms of being an internet addict:
>
> 25. You believe nothing looks sexier than a man in boxer shorts illuminated
>
> only by a 17" inch svga monitor.
>
>
>
> /// 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 ///
After some more digging, I gather you are referring to settmode(), where the
options are TMODE_COOK, TMODE_SLEEP, and TMODE_RAW. TMODE_COOK allows directly
typing characters on screen even while I have Vim stopped at a breakpoint in
gdb. Using TMODE_SLEEP in mch_call_shell() in unix.c instead of TMODE_COOK
makes the problem go away and system() commands still work, but I don't know
what the side effects would be. I'm having a hard time looking up cooked shells
without finding articles about seafood :)
--
--
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/d/optout.
