Lines Matching refs:commands

395 roles to highlight the commands in a meaningful way:
439 commands and output.  Smart syntax highlighting is also supported (using the
478 * ``console`` for console output, i.e. interactive shell sessions where commands are prefixed by a
480   shown. The commands will be highlighted, and the output will not. What's more, copying code block
481   using the "copy" button will automatically copy just the commands, excluding the prompt and the
482   outputs of the commands.
483 * ``shell`` or ``bash`` for shell commands. Both languages get highlighted the same but you may use
484   ``bash`` for conveying that the commands are bash-specific, and ``shell`` for generic shell
485   commands.
503         * - One or several commands, no output
529         * - An interactive Zephyr shell session, with commands and their outputs
784 Application build commands
787 .. rst:directive:: .. zephyr-app-commands::
789    Generate consistent documentation of the shell commands needed to manage (build, flash, etc.) an
792    For example, to generate commands to build ``samples/hello_world`` for ``qemu_x86`` use::
794       .. zephyr-app-commands::
801       .. zephyr-app-commands::
848       If set, build commands will target the given board.
853       If set, build commands will target the given shield.
859       If set, build commands will use the given configuration file(s).