nvi/ex/ex.c

13 static const char sccsid[] = "$Id: ex.c,v 10.80 2012/10/03 16:24:40 zy Exp $";
44  * ex --
45  *	Main ex loop.
47  * PUBLIC: int ex __P((SCR **));
50 ex(SCR **spp)
63 	/* Start the ex screen. */
84 	 * applied to ex command input read from a file.  In addition, the
169  *	The guts of the ex parser: parse and execute a string containing
170  *	ex commands.
178  * For the fun of it, if you want to see if a vi clone got the ex argument
270 	 * ex/vi allowed a single extra one.  It's simpler not to count.
309 	 * Historically, in ex mode, lines containing only <blank> characters
337 	 * command character, but this is the ex parser, and I've been wrong
361 	 * If no command, ex does the last specified of p, l, or #, and vi
411 		 * Capital letters beginning the command names ex, edit,
487 		 * from ex than when called from a vi colon command.  FMH.
564 	 * Historically, the number option applied to both ex and vi.  One
565 	 * strangeness was that ex didn't switch display formats until a
575 	/* Check for ex mode legality. */
578 		    "082|%s: command not available in ex mode");
588 	 * There are three normal termination cases for an ex command.  They
598 	 * 2: The ex, edit, next and visual in vi mode commands all take ex
603 	 * Historically, '|' characters in the first argument of the ex, edit,
619 	 * was also legal, i.e. the historic ex parser (using the word loosely,
842 	 * (ex: z) care if the user specified an address or if we just used
1036 			 * historic ex, and were used as buffers, not flags.
1044 			 * Digits can't be buffer names in ex commands, or the
1237 	 * because this is a place where all ex addresses pass through.
1248 		 * Historic ex/vi permitted commands with counts to go past
1250 		 * ex command "1,6>" would fail, but the command ">300"
1361 	 * command from the ex command loop and we're talking to a tty, and
1364 	 * the prompt character with the output.  Since ex runs in canonical
1367 	 * be in ex mode so we'll do nothing.
1378 	 * Call the underlying function for the ex command.
1405 	 * Executing ex commands from vi only reported the final modified
1481 	 * before we finish executing any more of this ex command.  For
1532 	 * we continue with the rest of the ex command(s), operating on the
1617  *	Get a line range for ex commands, or perform a vi ex address search.
1658 			/* Vi ex address searches didn't permit % signs. */
1693 			/* Vi ex address searches didn't permit commas. */
1773 	 * Vi ex address searches are indifferent to order or trailing
1809  * motion set it.  While ex/vi wasn't totally consistent about this, ANY
2160  *	Discard any pending ex commands.
2218  *	The vi text input routine needs to know if ex thinks this is an
2235  *	The vi text input routine needs to know if ex thinks this is an
2343  *	Log ex commands.