| /openbsd-src/gnu/usr.bin/binutils/gdb/testsuite/gdb.base/ |
| H A D | commands.exp | 26 # test special commands (if, while, etc)
33 set binfile ${objdir}/${subdir}/commands
153 send_gdb "commands\n"
156 pass "commands in if_while_breakpoint_command_test"
159 fail "(timeout or eof) commands in if_while_breakpoint_command_test"
165 "commands part 2 in if_while_breakpoint_command_test"
175 # Test that we can run the inferior from breakpoint commands.
177 # The expected behavior is that all commands after the first "step"
178 # shall be ignored. See the gdb manual, "Break Commands",
197 # part1: issue the gdb command "commands"
[all …]
|
| H A D | freebpcmd.exp | 21 # of commands to it, including a "continue" command. Run the program,
22 # so that the breakpoint is hit, its commands get executed, and the
29 # calls execute_control_command to run the commands. The 'continue'
36 # -> frees the commands we are currently running.
88 send_gdb "commands\n"
105 pass "send breakpoint commands"
107 fail "send breakpoint commands ($reason)"
111 gdb_test_multiple "" "run program with breakpoint commands" {
113 kfail "gdb/1489" "run program with breakpoint commands"
116 pass "run program with breakpoint commands"
[all …]
|
| H A D | page.exp | 39 "List of classes of commands:"
41 "aliases -- Aliases of other commands"
45 "internals -- Maintenance commands"
52 "user-defined -- User-defined commands"
54 "Type .help. followed by a class name for a list of commands in that class."
66 "List of classes of commands:"
68 "aliases -- Aliases of other commands"
72 "internals -- Maintenance commands"
|
| /openbsd-src/usr.bin/sed/USD.doc/ |
| H A D | sed | 75 of editing commands is too complicated to be comfortably
101 of editing commands is too complicated to be comfortably
160 perhaps performing one or more editing commands on each
175 The function must be present; the available commands are discussed
204 the file should contain editing commands, one to a line.
218 1.2. Order of Application of Editing Commands
221 even opened), all the editing commands are compiled into
223 the execution phase (when the commands are actually applied to
225 The commands are compiled in the order in which they are
228 The commands are applied one at a time; the input to each command
[all …]
|
| /openbsd-src/bin/csh/USD.doc/ |
| H A D | csh.2 | 41 directory and begins by reading commands from a file
46 We will later see what kinds of commands are usefully placed there.
53 will, after it reads commands from
55 read commands from a file
58 This file contains commands which you wish to do each time you log in
77 This file contains several commands to be executed by UNIX
114 print out statistics lines for commands which execute for at least 15 seconds
116 I want the shell to remember the last 10 commands I type in its
126 file and begin reading commands from the terminal, prompting for each with
131 will print `logout' and execute commands from the file `.logout'
[all …]
|
| H A D | csh.g | 131 Commands in UNIX receive a list of
158 Commands started without waiting for them to complete are called
160 commands (2.6).
188 heavily used commands and `/usr/bin' which contains most other user
216 Most commands in UNIX are not built into the shell,
220 These commands are accessible because the directories in which
364 It is one of the most commonly used UNIX commands (1.6).
510 Commands receiving input from a
515 Most commands terminate when they receive an
559 The commands
[all …]
|
| /openbsd-src/usr.bin/vi/docs/USD.doc/vi.ref/ |
| H A D | vi.cmd.roff | 19 commands, and for
61 There are several commands that change
99 is in the scrolling and screen oriented position commands:
112 these commands acted on physical (as opposed to logical, or screen)
115 screen, this meant that single line scroll commands might repaint the
116 entire screen, scrolling or screen positioning commands might not change
123 these commands act on logical, i.e. screen lines.
131 Each command description (for commands that alter the current cursor
169 commands.
199 commands.
[all …]
|
| H A D | vi.ref | 216 You can enter a normal editing window on the collected commands that
220 and then modify and/or execute the commands.
236 entering commands on the
285 mode) commands divide the screen into multiple editing regions and
314 commands provide usage information for all of the
318 commands by default, or, optionally, for a specific command or key.
330 commands, not
332 commands.
337 commands may not be used.
396 specific commands in the
[all …]
|
| H A D | set.opt.roff | 23 from all other commands for it to be accepted, in
57 .QB "Ex Commands" .
88 commands, or the
94 commands) the new line is automatically indented to align the cursor with
102 For commands inserting text into the middle of a line, any blank characters
149 commands change from the first nonblank of the line to the end of the
157 commands
173 commands, and for any command where optional flags are used to explicitly
184 commands, and the
195 commands automatically write the current file back to the current file name
[all …]
|
| /openbsd-src/gnu/usr.bin/binutils/gdb/testsuite/gdb.hp/gdb.aCC/ |
| H A D | watch-cmd.exp | 25 # test special commands
68 # Verify that we can create a watchpoint, and give it a commands
84 send_gdb "commands $wp_id\n"
86 -re "Type commands for when breakpoint $wp_id is hit, one per line.*>"\
87 { pass "begin commands on watch"}
89 {fail "begin commands on watch"}
90 timeout {fail "(timeout) begin commands on watch"}
98 # send_gdb "commands $wp_id\n"
100 # -re "Type commands for when breakpoint $wp_id is hit, one per line.*>"\
101 # {pass "begin commands on watch"}
[all …]
|
| /openbsd-src/usr.bin/vi/docs/internals/ |
| H A D | quoting | 23 4: In the ex commands themselves.
25 1: Vi text input mode (a, i, o, :colon commands, etc.):
76 4: The ex commands:
78 Ex commands are delimited by '|' or newline characters.
79 Within the commands, whitespace characters delimit the
82 commands, control-V escapes the next character, instead.
88 Escaping characters in file names in ex commands:
108 4: Escaping characters in non-file arguments in ex commands:
119 These commands use whitespace to delimit their arguments, and use
133 4.1: The edit/ex commands:
[all …]
|
| /openbsd-src/gnu/llvm/lldb/tools/lldb-vscode/ |
| H A D | README.md | 93 …initCommands** |[string]| | LLDB commands executed upon debugger startup prior to creating the L…
94 …RunCommands** |[string]| | LLDB commands executed just before launching after the LLDB target has …
95 |**stopCommands** |[string]| | LLDB commands executed just after each stop. Commands and command …
96 |**exitCommands** |[string]| | LLDB commands executed when the program exits. Commands and comman…
97 |**terminateCommands** |[string]| | LLDB commands executed when the debugging session ends. Command…
120 …initCommands** |[string]| | LLDB commands executed upon debugger startup prior to creating the L…
121 …RunCommands** |[string]| | LLDB commands executed just before launching after the LLDB target has …
122 |**stopCommands** |[string]| | LLDB commands executed just after each stop. Commands and command …
123 |**exitCommands** |[string]| | LLDB commands executed when the program exits. Commands and comman…
124 |**terminateCommands** |[string]| | LLDB commands executed when the debugging session ends. Command…
[all …]
|
| H A D | package.json | 203 "description": "Initialization commands executed upon debugger startup.",
208 "description": "Commands executed just before the program is launched.",
213 …"description": "Commands executed just as soon as the program is successfully launched when it's i…
218 …commands that are executed instead of launching a process. A target will be created with the launc…
223 "description": "Commands executed each time the program stops.",
228 "description": "Commands executed at the end of debugging session.",
283 …commands that are executed instead of attaching to a process ID or to a process by name. These com…
288 "description": "Initialization commands executed upon debugger startup.",
293 "description": "Commands executed just before the program is attached to.",
298 …"description": "Commands executed just as soon as the program is successfully attached when it's i…
[all …]
|
| /openbsd-src/share/man/man1/ |
| H A D | intro.1 | 38 .Nd introduction to general commands (tools and utilities)
40 The manual pages in section 1 contain most of the commands which comprise the
43 Some of the commands included in section 1 are
47 file manipulation commands,
48 system status commands,
49 remote file copy commands,
50 mail commands,
53 and line printer commands.
55 All commands set a status value upon exit which may be tested
|
| /openbsd-src/bin/ksh/ |
| H A D | sh.1 | 33 it reads one or more commands,
36 and then sets about executing those commands.
57 Read commands from
60 Read commands from standard input
63 Read commands from
143 Read commands but do not execute them \(en
216 Execute the commands in
224 or zero if no commands were executed.
390 visible to subsequently run commands,
411 Edit commands from command history using
[all …]
|
| /openbsd-src/usr.bin/tmux/ |
| H A D | cmd-parse.y | 54 struct cmd_parse_commands *commands; member
83 struct cmd_parse_commands *commands; member
109 struct cmd_parse_commands *commands; member
111 struct cmd_parse_commands *commands; member
128 %type <commands> argument_statements statements statement
129 %type <commands> commands condition condition1
139 ps->commands = $1;
174 | commands
330 cmd_parse_free_commands($4.commands);
[all...] |
| /openbsd-src/bin/csh/ |
| H A D | csh.1 | 78 Commands are read from the (single) following argument which must
107 Commands are parsed, but not executed.
141 variable to be set, so that commands are echoed immediately before execution.
151 commands to be executed.
168 begins by executing commands from the file
174 commands from
188 In the normal case, the shell will begin reading commands from the
200 When a login shell terminates, it executes commands from the files
260 .Ss Commands
264 a sequence of simple commands separated by
[all …]
|
| /openbsd-src/gnu/llvm/lldb/include/lldb/Interpreter/ |
| H A D | CommandInterpreter.h | 63 /// control all the instances where we run multiple commands, e.g.
77 /// run is a signal or exception, stop executing the commands.
92 /// If \b true add the commands to the command history. If \b false, don't
235 eCommandTypesBuiltin = 0x0001, //< native commands such as "frame"
236 eCommandTypesUserDef = 0x0002, //< scripted commands
237 eCommandTypesUserMW = 0x0004, //< multiword commands (command containers)
239 eCommandTypesHidden = 0x0010, //< commands prefixed with an underscore
240 eCommandTypesAllThem = 0xFFFF //< all commands
244 // substituting for alias commands. They work by writing special tokens
299 /// and are all actual commands - not aliases, and the leaf command is a
[all …]
|
| /openbsd-src/usr.bin/vi/docs/USD.doc/vi.man/ |
| H A D | vi.1 | 96 is not limited to positioning commands.
162 will read commands from it regardless; however, the session will be a
181 The last line of the screen is used for you to give commands to
190 i.e. you are either entering text or you are executing commands,
193 There are commands that switch you into input mode.
229 The commands to move around the file are:
248 The commands to enter new text are:
265 commands, use
270 The commands to copy text are:
278 The commands to delete text are:
[all …]
|
| /openbsd-src/bin/ln/ |
| H A D | symlink.7 | 57 Historically, commands and system calls have adopted their own
143 .Ss Commands not traversing a file tree
145 name arguments, to commands which are not traversing a file tree.
147 Except as noted below, commands follow symbolic links named as
158 It is important to realize that this rule includes commands which may
190 commands do not follow symbolic links named as arguments,
250 commands follow symbolic links specified on the command line
254 .Ss Commands traversing a file tree
255 The following commands either optionally or always traverse file trees:
313 As consistently as possible, it is possible to make commands doing a file tree
[all …]
|
| /openbsd-src/gnu/usr.bin/binutils/gdb/cli/ |
| H A D | cli-decode.h | 30 /* Not a set/show command. Note that some commands which begin with
45 /* This flag is used by the code executing commands to warn the user
65 names and for help topics that are not really commands. NOTE:
104 allocated. In some cases it makes sense to deprecate commands
134 /* For prefix commands only:
135 String containing prefix commands to get here: this one
138 commands reached through this prefix. */
141 /* For prefix commands only:
147 be mentioned in lists of commands.
180 /* Pointer to command strings of user-defined commands */
[all …]
|
| /openbsd-src/share/man/man4/ |
| H A D | ipmi.4 | 58 IPMI request messages are commonly referred to as commands.
61 IPMI commands are grouped into functional command sets
63 There are command sets for sensor and event related commands,
64 chassis commands etc.
71 IPMI provides access by abstracted sensor commands
87 A set of IPMI commands allows the SEL to be read and cleared
91 .Sh SENSOR DATA RECORDS & CAPABILITIES COMMANDS
102 Capabilities Commands and Sensor Data Records (SDRs).
103 Capabilities commands are commands within the IPMI command sets that return
104 fields that provide information on other commands and functions the controller
|
| /openbsd-src/gnu/usr.bin/binutils/etc/ |
| H A D | make-stds.texi | 41 * Command Variables:: Variables for Specifying Commands
44 * Install Command Categories:: Three categories of commands in the `install'
145 Write the Makefile commands (and any shell scripts, such as
208 @section Variables for Specifying Commands
210 Makefiles should provide variables for overriding certain commands, options,
237 compilation commands or by defining an implicit rule, like this:
266 commands for actual installation, for executables and nonexecutables
288 the installation commands. Use a separate command for each file to be
471 The Makefile commands should check whether the value of
589 The commands should create all the directories in which files are to be
[all …]
|
| /openbsd-src/gnu/usr.bin/binutils-2.17/etc/ |
| H A D | make-stds.texi | 41 * Command Variables:: Variables for Specifying Commands
44 * Install Command Categories:: Three categories of commands in the `install'
145 Write the Makefile commands (and any shell scripts, such as
208 @section Variables for Specifying Commands
210 Makefiles should provide variables for overriding certain commands, options,
237 compilation commands or by defining an implicit rule, like this:
266 commands for actual installation, for executables and nonexecutables
288 the installation commands. Use a separate command for each file to be
471 The Makefile commands should check whether the value of
589 The commands should create all the directories in which files are to be
[all …]
|
| /openbsd-src/usr.bin/vi/vi/ |
| H A D | v_left.c | 38 * The ^H and h commands always failed in the first column. in v_left()
53 * All commands move to the end of the range. Motion commands in v_left()
122 * Delete and non-motion commands move to the end of the range, in v_cfirst()
168 * If moving right, non-motion commands move to the end of the range. in v_first()
169 * Delete and yank stay at the start. Motion commands adjust the in v_first()
172 * If moving left, all commands move to the end of the range. Motion in v_first()
173 * commands adjust the starting point to the character before the in v_first()
230 * If moving right, non-motion commands move to the end of the range. in v_ncol()
231 * Delete and yank stay at the start. Motion commands adjust the in v_ncol()
234 * If moving left, all commands move to the end of the range. Motion in v_ncol()
[all …]
|