9 Commits

Author	SHA1	Message	Date
Ondrej Zajicek	e0a45fb421	Restricted read-only CLI. ... Also adds support for executing commands using birdc <cmd>.	2010-02-21 09:57:26 +01:00
Ondrej Zajicek	6baef17ecf	Fixes bug in CLI TX buffer management.	2009-07-14 14:18:54 +02:00
Martin Mares	4b87e256eb	Split off general commands to cmds.c. ... Added `show symbols' command which dumps whole symbol table together with symbol types etc.	2000-01-19 12:30:19 +00:00
Martin Mares	34350a5270	Implemented echoing of log messages to CLI connections. Just try `echo all'.	1999-12-06 12:34:45 +00:00
Martin Mares	3579376927	cli_msg() moved to cli.h, so that it can be used outside the parser.	1999-11-25 15:34:51 +00:00
Martin Mares	ffb59d243a	Command line interface now works.	1999-11-17 12:00:21 +00:00
Martin Mares	bc2fb68098	Parse CLI commands. We use the same parser as for configuration files (because ... we want to allow filter and similar complex constructs to be used in commands and we should avoid code duplication), only with CLI_MARKER token prepended before the whole input. Defined macro CF_CLI(cmd, args, help) for defining CLI commands in .Y files. The first argument specifies the command itself, the remaining two arguments are copied to the help file (er, will be copied after the help file starts to exist). This macro automatically creates a skeleton rule for the command, you only need to append arguments as in: CF_CLI(STEAL MONEY, <$>, [[Steal <$> US dollars or equivalent in any other currency]]): NUM { cli_msg(0, "%d$ stolen", $3); } ; Also don't forget to reset lexer state between inputs.	1999-10-31 17:47:47 +00:00
Martin Mares	b9672a845f	The CLI I/O functions work as desired.	1999-10-31 15:43:44 +00:00
Martin Mares	7d3aab1c16	First steps of the Command Line Interface: I/O routines.	1999-10-29 12:10:10 +00:00