Lines Matching full:vi

1 There are six (normally) asynchronous actions about which vi cares:
16 	can they handle interrupted system calls, so the vi routines that
22 	switched vi into ex mode, and we continue that practice.
27 	that the screen will not resize until vi runs out of keys, but
30 SIGINT and SIGTSTP are a much more difficult issue to resolve.  Vi has
34 worse as more complex semantics are added to vi, especially things like
45 	historic implementations of vi).  Periodically reading the terminal
51 	the historic version of vi didn't permit you to suspend the screen if
52 	you were on the colon command line.  This isn't right.  ^Z isn't a vi
58 	on DISCARD and LNEXT.  To clarify, what vi WANTS is 8-bit clean, with
70 	The second problem is that vi permits you to enter literal signal
74 	before vi reads the ^V.  (This is particularly problematic if you're
77 	character in vi, but that means that there's a race between entering
82 	Generally, this is what historic vi did.  (It didn't have the curses
95 	requires interaction or state between the vi parser and the key
110 	don't have to worry about synchronizing between the vi parser and the
143 like this: the shell execs the mail program, which execs vi.  The user hits
150 that somewhere in the middle of all of this, vi is resetting the terminal,
152 itself to sleep.  There's a solution to all of this: when vi starts, it puts
159 processes vi may fork off.  If vi calls ex, ex resets the terminal and
160 starts running some filter, and SIGTSTP stops them both, vi has to know