dist/ex/ex.c

1 /*	$NetBSD: ex.c,v 1.7 2017/11/22 13:13:18 rin Exp $ */
16 static const char sccsid[] = "Id: ex.c,v 10.75 2004/03/16 14:13:35 skimo Exp  (Berkeley) Date: 2004/03/16 14:13:35 ";
19 __RCSID("$NetBSD: ex.c,v 1.7 2017/11/22 13:13:18 rin Exp $");
52  * ex --
53  *	Main ex loop.
55  * PUBLIC: int ex __P((SCR **));
58 ex(SCR **spp)
71 	/* Start the ex screen. */
92 	 * applied to ex command input read from a file.  In addition, the
178  *	The guts of the ex parser: parse and execute a string containing
179  *	ex commands.
187  * For the fun of it, if you want to see if a vi clone got the ex argument
282 	 * ex/vi allowed a single extra one.  It's simpler not to count.
321 	 * Historically, in ex mode, lines containing only <blank> characters
349 	 * command character, but this is the ex parser, and I've been wrong
373 	 * If no command, ex does the last specified of p, l, or #, and vi
423 		 * Capital letters beginning the command names ex, edit,
499 		 * from ex than when called from a vi colon command.  FMH.
576 	 * Historically, the number option applied to both ex and vi.  One
577 	 * strangeness was that ex didn't switch display formats until a
587 	/* Check for ex mode legality. */
590 		    "082|%s: command not available in ex mode");
600 	 * There are three normal termination cases for an ex command.  They
610 	 * 2: The ex, edit, next and visual in vi mode commands all take ex
615 	 * Historically, '|' characters in the first argument of the ex, edit,
631 	 * was also legal, i.e. the historic ex parser (using the word loosely,
850 	 * (ex: z) care if the user specified an address or if we just used
1044 			 * historic ex, and were used as buffers, not flags.
1052 			 * Digits can't be buffer names in ex commands, or the
1244 	 * because this is a place where all ex addresses pass through.
1255 		 * Historic ex/vi permitted commands with counts to go past
1257 		 * ex command "1,6>" would fail, but the command ">300"
1369 	 * command from the ex command loop and we're talking to a tty, and
1372 	 * the prompt character with the output.  Since ex runs in canonical
1375 	 * be in ex mode so we'll do nothing.
1386 	 * Call the underlying function for the ex command.
1413 	 * Executing ex commands from vi only reported the final modified
1489 	 * before we finish executing any more of this ex command.  For
1540 	 * we continue with the rest of the ex command(s), operating on the
1625  *	Get a line range for ex commands, or perform a vi ex address search.
1662 			/* Vi ex address searches didn't permit % signs. */
1697 			/* Vi ex address searches didn't permit commas. */
1777 	 * Vi ex address searches are indifferent to order or trailing
1813  * motion set it.  While ex/vi wasn't totally consistent about this, ANY
2159  *	Discard any pending ex commands.
2209  *	The vi text input routine needs to know if ex thinks this is an
2226  *	The vi text input routine needs to know if ex thinks this is an
2334  *	Log ex commands.