| /dports/lang/python-tools/Python-3.8.12/Doc/library/ |
| H A D | pdb.rst | 18 evaluation of arbitrary Python code in the context of any stack frame. It also
57 restarting preserves pdb's state (such as breakpoints) and in most cases is more
214 square brackets (``[]``) in the command syntax; the square brackets must not be
215 typed. Alternatives in the command syntax are separated by a vertical bar
222 and are executed in the context of the program being debugged. Python
226 statement, the exception name is printed but the debugger's state is not
230 parameters which allows one a certain level of adaptability to the context under
241 triple: debugger; configuration; file
266 indicates the current frame, which determines the context of most commands.
436 Evaluate the *expression* in the current context and print its value.
[all …]
|
| /dports/lang/python39/Python-3.9.9/Doc/library/ |
| H A D | pdb.rst | 18 evaluation of arbitrary Python code in the context of any stack frame. It also
57 restarting preserves pdb's state (such as breakpoints) and in most cases is more
214 square brackets (``[]``) in the command syntax; the square brackets must not be
215 typed. Alternatives in the command syntax are separated by a vertical bar
222 and are executed in the context of the program being debugged. Python
226 statement, the exception name is printed but the debugger's state is not
230 parameters which allows one a certain level of adaptability to the context under
241 triple: debugger; configuration; file
266 indicates the current frame, which determines the context of most commands.
436 Evaluate the *expression* in the current context and print its value.
[all …]
|
| /dports/x11-toolkits/py-tkinter/Python-3.8.12/Doc/library/ |
| H A D | pdb.rst | 18 evaluation of arbitrary Python code in the context of any stack frame. It also
57 restarting preserves pdb's state (such as breakpoints) and in most cases is more
214 square brackets (``[]``) in the command syntax; the square brackets must not be
215 typed. Alternatives in the command syntax are separated by a vertical bar
222 and are executed in the context of the program being debugged. Python
226 statement, the exception name is printed but the debugger's state is not
230 parameters which allows one a certain level of adaptability to the context under
241 triple: debugger; configuration; file
266 indicates the current frame, which determines the context of most commands.
436 Evaluate the *expression* in the current context and print its value.
[all …]
|
| /dports/lang/python311/Python-3.11.0a3/Doc/library/ |
| H A D | pdb.rst | 18 evaluation of arbitrary Python code in the context of any stack frame. It also
57 restarting preserves pdb's state (such as breakpoints) and in most cases is more
214 square brackets (``[]``) in the command syntax; the square brackets must not be
215 typed. Alternatives in the command syntax are separated by a vertical bar
222 and are executed in the context of the program being debugged. Python
226 statement, the exception name is printed but the debugger's state is not
230 parameters which allows one a certain level of adaptability to the context under
241 triple: debugger; configuration; file
270 indicates the current frame, which determines the context of most commands.
440 Evaluate the *expression* in the current context and print its value.
[all …]
|
| /dports/www/chromium-legacy/chromium-88.0.4324.182/third_party/llvm/lldb/docs/status/ |
| H A D | projects.rst | 21 the context of the search, but let the search leak out globally. And quite
77 expressions run in that context to fail. We need to fix this by adjusting
93 over who gets to control the process state.
111 Add some syntax to generate data formatters from type definitions
223 We need to put the lldb syntax docs in the tutorial somewhere that is more
225 system, and then have a "help lldb" or "help syntax" type command with this
290 state at StopPoint 0, StopPoint 1, etc. These could then be used for testing
294 Expression parser needs syntax for "{symbol,type} A in CU B.cpp"
300 the syntax should support all these.
386 state of the thread if we let the exception escape the expression, we currently
[all …]
|
| /dports/devel/tinygo/tinygo-0.14.1/llvm-project/lldb/docs/status/ |
| H A D | projects.rst | 21 the context of the search, but let the search leak out globally. And quite
77 expressions run in that context to fail. We need to fix this by adjusting
93 over who gets to control the process state.
111 Add some syntax to generate data formatters from type definitions
223 We need to put the lldb syntax docs in the tutorial somewhere that is more
225 system, and then have a "help lldb" or "help syntax" type command with this
290 state at StopPoint 0, StopPoint 1, etc. These could then be used for testing
294 Expression parser needs syntax for "{symbol,type} A in CU B.cpp"
300 the syntax should support all these.
386 state of the thread if we let the exception escape the expression, we currently
[all …]
|
| /dports/devel/wasi-libcxx/llvm-project-13.0.1.src/lldb/docs/status/ |
| H A D | projects.rst | 21 the context of the search, but let the search leak out globally. And quite
77 expressions run in that context to fail. We need to fix this by adjusting
93 over who gets to control the process state.
111 Add some syntax to generate data formatters from type definitions
223 We need to put the lldb syntax docs in the tutorial somewhere that is more
225 system, and then have a "help lldb" or "help syntax" type command with this
290 state at StopPoint 0, StopPoint 1, etc. These could then be used for testing
294 Expression parser needs syntax for "{symbol,type} A in CU B.cpp"
300 the syntax should support all these.
386 state of the thread if we let the exception escape the expression, we currently
[all …]
|
| /dports/devel/llvm-cheri/llvm-project-37c49ff00e3eadce5d8703fdc4497f28458c64a8/lldb/docs/status/ |
| H A D | projects.rst | 21 the context of the search, but let the search leak out globally. And quite
77 expressions run in that context to fail. We need to fix this by adjusting
93 over who gets to control the process state.
111 Add some syntax to generate data formatters from type definitions
223 We need to put the lldb syntax docs in the tutorial somewhere that is more
225 system, and then have a "help lldb" or "help syntax" type command with this
290 state at StopPoint 0, StopPoint 1, etc. These could then be used for testing
294 Expression parser needs syntax for "{symbol,type} A in CU B.cpp"
300 the syntax should support all these.
386 state of the thread if we let the exception escape the expression, we currently
[all …]
|
| /dports/devel/llvm12/llvm-project-12.0.1.src/lldb/docs/status/ |
| H A D | projects.rst | 21 the context of the search, but let the search leak out globally. And quite
77 expressions run in that context to fail. We need to fix this by adjusting
93 over who gets to control the process state.
111 Add some syntax to generate data formatters from type definitions
223 We need to put the lldb syntax docs in the tutorial somewhere that is more
225 system, and then have a "help lldb" or "help syntax" type command with this
290 state at StopPoint 0, StopPoint 1, etc. These could then be used for testing
294 Expression parser needs syntax for "{symbol,type} A in CU B.cpp"
300 the syntax should support all these.
386 state of the thread if we let the exception escape the expression, we currently
[all …]
|
| /dports/lang/rust/rustc-1.58.1-src/src/llvm-project/lldb/docs/status/ |
| H A D | projects.rst | 21 the context of the search, but let the search leak out globally. And quite
77 expressions run in that context to fail. We need to fix this by adjusting
93 over who gets to control the process state.
111 Add some syntax to generate data formatters from type definitions
223 We need to put the lldb syntax docs in the tutorial somewhere that is more
225 system, and then have a "help lldb" or "help syntax" type command with this
290 state at StopPoint 0, StopPoint 1, etc. These could then be used for testing
294 Expression parser needs syntax for "{symbol,type} A in CU B.cpp"
300 the syntax should support all these.
386 state of the thread if we let the exception escape the expression, we currently
[all …]
|
| /dports/devel/llvm-devel/llvm-project-f05c95f10fc1d8171071735af8ad3a9e87633120/lldb/docs/status/ |
| H A D | projects.rst | 21 the context of the search, but let the search leak out globally. And quite
77 expressions run in that context to fail. We need to fix this by adjusting
93 over who gets to control the process state.
111 Add some syntax to generate data formatters from type definitions
223 We need to put the lldb syntax docs in the tutorial somewhere that is more
225 system, and then have a "help lldb" or "help syntax" type command with this
290 state at StopPoint 0, StopPoint 1, etc. These could then be used for testing
294 Expression parser needs syntax for "{symbol,type} A in CU B.cpp"
300 the syntax should support all these.
386 state of the thread if we let the exception escape the expression, we currently
[all …]
|
| /dports/devel/wasi-compiler-rt13/llvm-project-13.0.1.src/lldb/docs/status/ |
| H A D | projects.rst | 21 the context of the search, but let the search leak out globally. And quite
77 expressions run in that context to fail. We need to fix this by adjusting
93 over who gets to control the process state.
111 Add some syntax to generate data formatters from type definitions
223 We need to put the lldb syntax docs in the tutorial somewhere that is more
225 system, and then have a "help lldb" or "help syntax" type command with this
290 state at StopPoint 0, StopPoint 1, etc. These could then be used for testing
294 Expression parser needs syntax for "{symbol,type} A in CU B.cpp"
300 the syntax should support all these.
386 state of the thread if we let the exception escape the expression, we currently
[all …]
|
| /dports/devel/wasi-compiler-rt12/llvm-project-12.0.1.src/lldb/docs/status/ |
| H A D | projects.rst | 21 the context of the search, but let the search leak out globally. And quite
77 expressions run in that context to fail. We need to fix this by adjusting
93 over who gets to control the process state.
111 Add some syntax to generate data formatters from type definitions
223 We need to put the lldb syntax docs in the tutorial somewhere that is more
225 system, and then have a "help lldb" or "help syntax" type command with this
290 state at StopPoint 0, StopPoint 1, etc. These could then be used for testing
294 Expression parser needs syntax for "{symbol,type} A in CU B.cpp"
300 the syntax should support all these.
386 state of the thread if we let the exception escape the expression, we currently
[all …]
|
| /dports/devel/llvm13/llvm-project-13.0.1.src/lldb/docs/status/ |
| H A D | projects.rst | 21 the context of the search, but let the search leak out globally. And quite
77 expressions run in that context to fail. We need to fix this by adjusting
93 over who gets to control the process state.
111 Add some syntax to generate data formatters from type definitions
223 We need to put the lldb syntax docs in the tutorial somewhere that is more
225 system, and then have a "help lldb" or "help syntax" type command with this
290 state at StopPoint 0, StopPoint 1, etc. These could then be used for testing
294 Expression parser needs syntax for "{symbol,type} A in CU B.cpp"
300 the syntax should support all these.
386 state of the thread if we let the exception escape the expression, we currently
[all …]
|
| /dports/editors/nano/nano-5.9/ |
| H A D | ChangeLog | 43 gnulib: update to its current upstream state
119 gnulib: update to its current upstream state
187 gnulib: update to its current upstream state
272 gnulib: update to its current upstream state
3349 syntax: python: don't require a character after an opening triple quote
3437 gnulib: update to its current state
3522 gnulib: update to its current state
3557 gnulib: update to its current state
3706 gnulib: update to current state
4404 chars: look at bytes in their context, so only valid sequences are accepted
[all …]
|
| /dports/devel/gitlab-runner/gitlab-runner-8925d9a06fd8e452e2161a768462652a2a13111f/docs/configuration/ |
| H A D | advanced-configuration.md | 180 | `builds_dir` | Absolute path to a directory where builds are stored in the context of the…
241 | `bash` | Generate Bash (Bourne-shell) script. All commands executed in Bash context. Defau…
242 | `sh` | Generate Sh (Bourne-shell) script. All commands executed in Sh context. The fallb…
288 | `volumes` | Additional volumes that should be mounted. Same syntax as the Do…
541 | `IdleCount` | Number of machines that need to be created and waiting in _Idle_ state. |
542 | `IdleTime` | Time (in seconds) for machine to be in _Idle_ state before it is removed. |
558 | `IdleCount` | Number of machines that need to be created and waiting in _Idle_ state. |
559 | `IdleTime` | Time (in seconds) for a machine to be in _Idle_ state before it is removed.…
591 ### Periods syntax
602 values, ranges, lists, and asterisks. View [a detailed description of the syntax](https://github.co…
[all …]
|
| /dports/misc/urbit/urbit-urbit-0.6.0/Spec/ |
| H A D | u3.md | 96 Hungarian syntax. This is weird, but works really well, as long
493 Normally in this context you assume you're obeying the rules of
732 [formula [sample context]]
885 A clue is a triple of name, parent, and hooks:
897 [formula [sample context]]
899 Typically the `context` is itself a library core, which itself
977 The `cope` is a triple of `++bane` (battery name, right now just
991 context. For example, your jet-propelled library function is
993 If you've replaced the kernel in your context with something
1021 A `calx` is a triple of a `++calf`, a `[bash cope]` cell, and a
[all …]
|
| /dports/textproc/raptor/raptor-1.4.21/ |
| H A D | ChangeLog.4 | 11 (raptor_syntaxes_enumerate): Added to get syntax name, label,
382 last_char recorded in state.
462 ntriples parser context.
799 Do nothing if some part of the triple
829 to pass on a general syntax error.
839 * examples/grapper.c: Add n3 syntax
875 (raptor_free_triple): Actually free the triple.
1646 to control rdf:type rdf:List triple generation from
1655 Remove rdf:type rdf:List triple
2446 Use URI from context.
[all …]
|
| /dports/textproc/raptor2/raptor2-2.0.15/ |
| H A D | ChangeLog.4 | 11 (raptor_syntaxes_enumerate): Added to get syntax name, label,
382 last_char recorded in state.
462 ntriples parser context.
799 Do nothing if some part of the triple
829 to pass on a general syntax error.
839 * examples/grapper.c: Add n3 syntax
875 (raptor_free_triple): Actually free the triple.
1646 to control rdf:type rdf:List triple generation from
1655 Remove rdf:type rdf:List triple
2446 Use URI from context.
[all …]
|
| /dports/editors/emacs/emacs-27.2/doc/misc/ |
| H A D | viper.texi | 782 precise history to be perused depends on the context. It may be the history
1244 @vindex viper-syntax-preference
1245 @cindex syntax table
1282 @findex viper-set-syntax-preference
1716 the context. If the value is negative, don't scroll.
2227 line to be re-indented in accordance with the context. In programming,
2635 On a triple-click, the region consists of the entire line where the click
2648 case of a triple-click, the prefix argument is ignored.)
2854 The syntax is:
3202 @vindex viper-syntax-preference
[all …]
|
| /dports/editors/emacs-devel/emacs-4d1968b/doc/misc/ |
| H A D | viper.texi | 782 precise history to be perused depends on the context. It may be the history
1244 @vindex viper-syntax-preference
1245 @cindex syntax table
1282 @findex viper-set-syntax-preference
1716 the context. If the value is negative, don't scroll.
2224 line to be re-indented in accordance with the context. In programming,
2632 On a triple-click, the region consists of the entire line where the click
2645 case of a triple-click, the prefix argument is ignored.)
2851 The syntax is:
3199 @vindex viper-syntax-preference
[all …]
|
| /dports/textproc/texi2html/texi2html-5.0/test/misc/res/texi_viper/ |
| H A D | viper.texi.first | 729 precise history to be perused depends on the context. It may be the history
1185 @vindex @code{viper-syntax-preference}
1186 @cindex syntax table
1220 (viper-set-syntax-preference nil "emacs")
1649 the context. If the value is negative---don't scroll.
2180 line to be re-indented in accordance with the context. In programming,
2565 On a triple-click, the region consists of the entire line where the click
2578 case of a triple-click, the prefix argument is ignored.)
2785 The syntax is:
3135 @vindex @code{viper-syntax-preference}
[all …]
|
| H A D | viper.texi | 741 precise history to be perused depends on the context. It may be the history
1197 @vindex @code{viper-syntax-preference}
1198 @cindex syntax table
1232 (viper-set-syntax-preference nil "emacs")
1661 the context. If the value is negative---don't scroll.
2192 line to be re-indented in accordance with the context. In programming,
2577 On a triple-click, the region consists of the entire line where the click
2590 case of a triple-click, the prefix argument is ignored.)
2797 The syntax is:
3147 @vindex @code{viper-syntax-preference}
[all …]
|
| /dports/textproc/texi2html/texi2html-5.0/test/misc/res_all/texi_viper/ |
| H A D | viper.texi | 741 precise history to be perused depends on the context. It may be the history
1197 @vindex @code{viper-syntax-preference}
1198 @cindex syntax table
1232 (viper-set-syntax-preference nil "emacs")
1661 the context. If the value is negative---don't scroll.
2192 line to be re-indented in accordance with the context. In programming,
2577 On a triple-click, the region consists of the entire line where the click
2590 case of a triple-click, the prefix argument is ignored.)
2797 The syntax is:
3147 @vindex @code{viper-syntax-preference}
[all …]
|
| /dports/textproc/texi2html/texi2html-5.0/test/misc/res_info/texi_viper/ |
| H A D | viper.texi | 741 precise history to be perused depends on the context. It may be the history
1197 @vindex @code{viper-syntax-preference}
1198 @cindex syntax table
1232 (viper-set-syntax-preference nil "emacs")
1661 the context. If the value is negative---don't scroll.
2192 line to be re-indented in accordance with the context. In programming,
2577 On a triple-click, the region consists of the entire line where the click
2590 case of a triple-click, the prefix argument is ignored.)
2797 The syntax is:
3147 @vindex @code{viper-syntax-preference}
[all …]
|