Bram,
> Can a few people, especially those with plugins that use system(), try this
> out?
I'll spent more time for checking it and also ask other people to test it.
Besides, I have to tell you there are only a few risk around this change.
As you know, system() separates the pair of stdin/stdout from vim's TTY for
child process.
But this is just a fake solution. Using the following solution, the child
process can re-connect the vim's stdin.
:call system('something-intractive-command < /dev/stdin > /dev/stdout')
If 'something-intractive-command' does not set termios state properly at the
start up time, the compatibility of command behavior can be lost, since
'something-intractive-command' and vim share the state of termios.
The point at issue is whether you allows such hack.
In my individual opinion, we need not assure the strict compatibility against
such behavior.
I think interactive(read something from key input from terminal) command must
not run in system() function.
I'll try to search the existing plugin which does such hack.
--
--
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.
