Lines Matching full:commands
19 * Support for static and dynamic commands.
20 * Support for dictionary commands.
22 * Built-in commands: :command:`clear`, :command:`shell`, :command:`colors`,
24 * Viewing recently executed commands using keys: :kbd:`↑` :kbd:`↓` or meta keys.
29 * Support for editing multiline commands.
30 * Built-in handler to display help for the commands.
72 By default the telnet client won't handle telnet commands and configuration. Although
74 This will give the telnet client access to a very limited set of supported commands but
174 Commands section in Shell
177 Shell commands are organized in a tree structure and grouped into the following
223 Creating commands
226 Use the following macros for adding shell commands:
228 * :c:macro:`SHELL_CMD_REGISTER` - Create root command. All root commands must
231 set) create root command. All root commands must have different name.
233 All root commands must have different name.
235 is set) create root command with arguments. All root commands must have
252 Commands can be created in any file in the system that includes
253 :zephyr_file:`include/zephyr/shell/shell.h`. All created commands are available for all
256 Static commands argument
264 :alt: Command tree with static commands.
276 SHELL_CMD_REGISTER(demo, &sub_demo, "Demo commands", NULL);
281 Dictionary commands
283 This is a special kind of static commands. Dictionary commands can be used
326 :alt: Dictionary commands example.
328 Dynamic commands argument
332 subcommands. At the beginning dynamic command list is empty. New commands
339 Newly added commands can be prompted or autocompleted with the :kbd:`Tab` key.
343 :alt: Command tree with static and dynamic commands.
347 /* Buffer for 10 dynamic commands */
350 /* commands counter */
365 /* if there are no more dynamic commands available
383 "Show all commands in dynamic_cmd_buffer.",
393 Commands execution argument
401 Commands can be also executed from a user application using any active backend
421 Commands execution example
432 :alt: Command tree with static commands.
494 The help for commands and subcommands can be created with respective macros:
501 Parent commands
505 commands or the parent commands, depending on how you index ``argv``.
509 commands.
534 Built-in commands
537 These commands are activated by :kconfig:option:`CONFIG_SHELL_CMDS` set to ``y``.
540 * :command:`history` - Shows the recently entered commands.
567 The Tab button can be used to suggest commands or subcommands. This feature
569 It can also be used for partial or complete auto-completion of commands.
576 * Prompts available commands and if possible partly completes the command.
577 * Will not do anything if there are no available or matching commands.
588 This feature enables commands history in the shell. It is activated by:
592 Number of commands that can be stored depends on size
720 An example of login and logout commands using this feature is located in
826 SHELL_CMD_REGISTER(demo, &sub_demo, "Demo commands", NULL);
836 commands:
848 These commands are registered by various modules, for example:
851 are built-in commands which have been registered by