Lines Matching full:ex
50 * Switch the editor into EX mode.
64 "207|The Q command requires the ex terminal interface"); in v_exmode()
74 /* Switch to ex mode. */ in v_exmode()
100 * current and next lines. This doesn't map well into the ex command in v_join()
242 * manipulating the ex argument structures behind ex's back. in v_filter()
303 * Execute an ex command.
331 * If we put out more than a single line of messages, or ex trashes in v_ex()
332 * the screen, the user may continue entering ex commands. We find in v_ex()
334 * completely into ex mode however, because the user can elect to in v_ex()
341 * There may already be an ex command waiting to run. If in v_ex()
389 * it. See, we resolved the output from the last ex command, in v_ex()
391 * where we have control before the ex command writes output. in v_ex()
394 * this command. This fixes a bug where combinations of ex in v_ex()
400 /* Call the ex parser. */ in v_ex()
403 /* Flush ex messages. */ in v_ex()
423 * If the user previously continued an ex command, we have to do in v_ex()
433 /* Cleanup from the ex command. */ in v_ex()
446 * Cleanup from an ex command.
458 * Ex keeps track of the line number, but it cares less about the in v_ex_done()
464 * Ex will soon have to start handling the column correctly; see in v_ex_done()
477 * Don't re-adjust the cursor after executing an ex command, in v_ex_done()
478 * and ex movements are permanent. in v_ex_done()
555 msgq(sp, M_BERR, "307|No ex command to execute"); in v_ecl_exec()