| /dports/editors/emacs-devel/emacs-4d1968b/lisp/cedet/ |
| H A D | ChangeLog.1 | 454 * semantic/ctxt.el (semantic-get-local-variables-default):
457 complete local variables.
979 * semantic/bovine/c.el (semantic-get-local-variables): Also add a
1077 `enable-local-variables' to `:safe' when loading files.
1409 * semantic/wisent/java-tags.el (semantic-get-local-variables):
1445 (srecode-get-mode-table): Find the mode, but also find all parent
1832 * semantic/ctxt.el (semantic-get-local-variables):
1912 * semantic/wisent/javascript.el (semantic-get-local-variables):
2681 (semantic-get-local-variables, semantic-end-of-command)
2688 (semantic-lex, semantic-get-local-variables, python-mode):
[all …]
|
| /dports/editors/emacs/emacs-27.2/lisp/cedet/ |
| H A D | ChangeLog.1 | 454 * semantic/ctxt.el (semantic-get-local-variables-default):
457 complete local variables.
979 * semantic/bovine/c.el (semantic-get-local-variables): Also add a
1077 `enable-local-variables' to `:safe' when loading files.
1409 * semantic/wisent/java-tags.el (semantic-get-local-variables):
1445 (srecode-get-mode-table): Find the mode, but also find all parent
1832 * semantic/ctxt.el (semantic-get-local-variables):
1912 * semantic/wisent/javascript.el (semantic-get-local-variables):
2681 (semantic-get-local-variables, semantic-end-of-command)
2688 (semantic-lex, semantic-get-local-variables, python-mode):
[all …]
|
| /dports/devel/boost-python-libs/boost_1_72_0/libs/xpressive/doc/ |
| H A D | actions.qbk | 98 // Here, _ refers back to all the
110 The answer is that by default, actions are executed /lazily/. When a sub-expression
147 // count all the digits.
163 So far, we've seen how to write semantic actions consisting of variables and
233 // OK, use as first(s1) to get the begin iterator
239 As we've seen in the examples above, we can refer to local variables within
268 value. That's not normally necessary because local variables appearing in
269 actions are held by value by default, but in this case, it is necessary. Had
273 It can be tedious to wrap all your variables in `ref()` and `val()` in your
312 assert( i.get() == 2 );
[all …]
|
| /dports/databases/xtrabackup/boost_1_59_0/libs/xpressive/doc/ |
| H A D | actions.qbk | 98 // Here, _ refers back to all the
110 The answer is that by default, actions are executed /lazily/. When a sub-expression
147 // count all the digits.
163 So far, we've seen how to write semantic actions consisting of variables and
233 // OK, use as first(s1) to get the begin iterator
239 As we've seen in the examples above, we can refer to local variables within
268 value. That's not normally necessary because local variables appearing in
269 actions are held by value by default, but in this case, it is necessary. Had
273 It can be tedious to wrap all your variables in `ref()` and `val()` in your
312 assert( i.get() == 2 );
[all …]
|
| /dports/databases/percona57-pam-for-mysql/boost_1_59_0/libs/xpressive/doc/ |
| H A D | actions.qbk | 98 // Here, _ refers back to all the
110 The answer is that by default, actions are executed /lazily/. When a sub-expression
147 // count all the digits.
163 So far, we've seen how to write semantic actions consisting of variables and
233 // OK, use as first(s1) to get the begin iterator
239 As we've seen in the examples above, we can refer to local variables within
268 value. That's not normally necessary because local variables appearing in
269 actions are held by value by default, but in this case, it is necessary. Had
273 It can be tedious to wrap all your variables in `ref()` and `val()` in your
312 assert( i.get() == 2 );
[all …]
|
| /dports/databases/mysqlwsrep57-server/boost_1_59_0/libs/xpressive/doc/ |
| H A D | actions.qbk | 98 // Here, _ refers back to all the
110 The answer is that by default, actions are executed /lazily/. When a sub-expression
147 // count all the digits.
163 So far, we've seen how to write semantic actions consisting of variables and
233 // OK, use as first(s1) to get the begin iterator
239 As we've seen in the examples above, we can refer to local variables within
268 value. That's not normally necessary because local variables appearing in
269 actions are held by value by default, but in this case, it is necessary. Had
273 It can be tedious to wrap all your variables in `ref()` and `val()` in your
312 assert( i.get() == 2 );
[all …]
|
| /dports/databases/percona57-server/boost_1_59_0/libs/xpressive/doc/ |
| H A D | actions.qbk | 98 // Here, _ refers back to all the
110 The answer is that by default, actions are executed /lazily/. When a sub-expression
147 // count all the digits.
163 So far, we've seen how to write semantic actions consisting of variables and
233 // OK, use as first(s1) to get the begin iterator
239 As we've seen in the examples above, we can refer to local variables within
268 value. That's not normally necessary because local variables appearing in
269 actions are held by value by default, but in this case, it is necessary. Had
273 It can be tedious to wrap all your variables in `ref()` and `val()` in your
312 assert( i.get() == 2 );
[all …]
|
| /dports/databases/percona57-client/boost_1_59_0/libs/xpressive/doc/ |
| H A D | actions.qbk | 98 // Here, _ refers back to all the
110 The answer is that by default, actions are executed /lazily/. When a sub-expression
147 // count all the digits.
163 So far, we've seen how to write semantic actions consisting of variables and
233 // OK, use as first(s1) to get the begin iterator
239 As we've seen in the examples above, we can refer to local variables within
268 value. That's not normally necessary because local variables appearing in
269 actions are held by value by default, but in this case, it is necessary. Had
273 It can be tedious to wrap all your variables in `ref()` and `val()` in your
312 assert( i.get() == 2 );
[all …]
|
| /dports/devel/boost-libs/boost_1_72_0/libs/xpressive/doc/ |
| H A D | actions.qbk | 98 // Here, _ refers back to all the
110 The answer is that by default, actions are executed /lazily/. When a sub-expression
147 // count all the digits.
163 So far, we've seen how to write semantic actions consisting of variables and
233 // OK, use as first(s1) to get the begin iterator
239 As we've seen in the examples above, we can refer to local variables within
268 value. That's not normally necessary because local variables appearing in
269 actions are held by value by default, but in this case, it is necessary. Had
273 It can be tedious to wrap all your variables in `ref()` and `val()` in your
312 assert( i.get() == 2 );
[all …]
|
| /dports/devel/boost-docs/boost_1_72_0/libs/xpressive/doc/ |
| H A D | actions.qbk | 98 // Here, _ refers back to all the
110 The answer is that by default, actions are executed /lazily/. When a sub-expression
147 // count all the digits.
163 So far, we've seen how to write semantic actions consisting of variables and
233 // OK, use as first(s1) to get the begin iterator
239 As we've seen in the examples above, we can refer to local variables within
268 value. That's not normally necessary because local variables appearing in
269 actions are held by value by default, but in this case, it is necessary. Had
273 It can be tedious to wrap all your variables in `ref()` and `val()` in your
312 assert( i.get() == 2 );
[all …]
|
| /dports/devel/hyperscan/boost_1_75_0/libs/xpressive/doc/ |
| H A D | actions.qbk | 98 // Here, _ refers back to all the
110 The answer is that by default, actions are executed /lazily/. When a sub-expression
147 // count all the digits.
163 So far, we've seen how to write semantic actions consisting of variables and
233 // OK, use as first(s1) to get the begin iterator
239 As we've seen in the examples above, we can refer to local variables within
268 value. That's not normally necessary because local variables appearing in
269 actions are held by value by default, but in this case, it is necessary. Had
273 It can be tedious to wrap all your variables in `ref()` and `val()` in your
312 assert( i.get() == 2 );
[all …]
|
| /dports/editors/emacs-devel/emacs-4d1968b/doc/misc/ |
| H A D | sem-user.texi | 69 The default value enables @semantic{} for all supported major modes
75 @defvar semantic-default-submodes
114 (@code{semantic-complete-jump-local}).
338 @item local
347 either, get the source, parse it, and create the table.
434 Alternately, you can get a list of include files @semantic{}
849 displays the methods and member variables.
881 You can also use @kbd{C-c , j} (@code{semantic-complete-jump-local})
951 list of headers @semantic{} is searching through. To get a basic
1004 @code{Localvar} should contain your local variables. @code{Scope}
[all …]
|
| H A D | semantic.texi | 12 @c Merge all indexes into a single index for now.
139 The words in all-capital are those that @semantic{} itself provides.
210 Parsing large files can take several seconds or more. By default,
285 under point, adding labels, and the all important
319 @code{semantic-test-all-format-tag-functions} to test different output
360 and allow a tag-search to span all available databases in that
376 get the full details.
401 the local context including the current prefix, and a tag list
408 The analyzer debugger. Useful when attempting to get everything
416 around through different scopes, get local variables, and collect the
[all …]
|
| /dports/editors/emacs/emacs-27.2/doc/misc/ |
| H A D | sem-user.texi | 69 The default value enables @semantic{} for all supported major modes
75 @defvar semantic-default-submodes
114 (@code{semantic-complete-jump-local}).
338 @item local
347 either, get the source, parse it, and create the table.
434 Alternately, you can get a list of include files @semantic{}
849 displays the methods and member variables.
881 You can also use @kbd{C-c , j} (@code{semantic-complete-jump-local})
951 list of headers @semantic{} is searching through. To get a basic
1004 @code{Localvar} should contain your local variables. @code{Scope}
[all …]
|
| H A D | semantic.texi | 12 @c Merge all indexes into a single index for now.
139 The words in all-capital are those that @semantic{} itself provides.
210 Parsing large files can take several seconds or more. By default,
285 under point, adding labels, and the all important
319 @code{semantic-test-all-format-tag-functions} to test different output
360 and allow a tag-search to span all available databases in that
376 get the full details.
401 the local context including the current prefix, and a tag list
408 The analyzer debugger. Useful when attempting to get everything
416 around through different scopes, get local variables, and collect the
[all …]
|
| /dports/editors/emacs/emacs-27.2/info/ |
| H A D | semantic.info | 211 (the default value of this variable sets up parsing for all the parsers
237 The default value enables Semantic for all supported major modes
242 -- Variable: semantic-default-submodes
284 (‘semantic-complete-jump-local’).
506 ‘local’
995 displays the methods and member variables.
1025 You can also use ‘C-c , j’ (‘semantic-complete-jump-local’) and ‘C-c
1141 contain your local variables. ‘Scope’ should contain datatypes in scope
1600 files to get the full details.
1639 around through different scopes, get local variables, and collect
[all …]
|
| /dports/lang/swi-pl/swipl-8.2.3/packages/jpl/docs/ |
| H A D | DeploymentLinux.md | 25 …as well as all associated documentation. However, these distribution-based packages are **highly o…
27 1. For Debian-based systems (Debian, Ubuntu, Mint, ...) you can get the latest stable and developme…
35 ## Configuring environment variables
37 …tion the right information, via environment variables, so that SWIPL is initialized properly and c…
49 SWI_HOME_DIR=/usr/lib/swi-prolog/ # if default binary not pointing to this version
50 LD_LIBRARY_PATH=/usr/lib/swi-prolog/lib/x86_64-linux/ # to find all .so, including libjpl.so
60 SWI_HOME_DIR=/usr/local/swipl-git/lib/swipl/ # if binary exec not pointing to this SWIPL
61 LD_LIBRARY_PATH=/usr/local/swipl-git/lib/swipl/lib/x86_64-linux/ # to find all .so, including l…
62 CLASSPATH=/usr/local/swipl-git/lib/swipl/lib/jpl.jar
69 …local/swipl-git/lib/swipl/lib/jpl.jar;LD_LIBRARY_PATH=/usr/local/swipl-git/lib/swipl/lib/x86_64-li…
[all …]
|
| /dports/editors/emacs-devel/emacs-4d1968b/etc/ |
| H A D | NEWS.28 | 309 local-variables section of a file.
408 'get-lru-window', 'get-mru-window' and 'get-largest-window' now accept a
1246 a list of symbols to try to get the "thing" at point. By default,
3337 Previously, if 'enable-local-variables' was nil, a 'lexical-binding'
3340 old behavior, set 'permanently-enabled-local-variables' to nil.
3350 ** 'kill-all-local-variables' has changed how it handles non-symbol hooks.
3351 The function is documented to eliminate all buffer-local bindings
3352 except variables with a 'permanent-local' property, or hooks that
3413 ** 'completing-read-default' sets completion variables buffer-locally.
3648 'semantic-flex-keyword-get', 'semantic-flex-keyword-p',
[all …]
|
| /dports/www/gitlab-workhorse/gitlab-foss-0a901d60f8ae4a60c04ae82e6e9c3a03e9321417/workhorse/vendor/github.com/uber/jaeger-client-go/ |
| H A D | README.md | 19 and [semantic versioning](http://semver.org/) when including this library into an application.
28 If you instead want to use the latest version in `master`, you can pull it via `go get`.
29 Note that during `go get` you may see build errors due to incompatible dependencies, which is why
30 we recommend using semantic versions for dependencies. The error may be fixed by running
34 go get -u github.com/uber/jaeger-client-go/
45 ### Environment variables
47 The tracer can be initialized with values coming from environment variables, if it is
72 JAEGER_TAGS | A comma separated list of `name=value` tracer-level tags, which get added to all repo…
80 variables.
195 * **Shared sampling state**: the sampling state is shared across all local
[all …]
|
| /dports/www/grafana8/grafana-8.3.6/vendor/github.com/cortexproject/cortex/vendor/github.com/uber/jaeger-client-go/ |
| H A D | README.md | 19 and [semantic versioning](http://semver.org/) when including this library into an application.
28 If you instead want to use the latest version in `master`, you can pull it via `go get`.
29 Note that during `go get` you may see build errors due to incompatible dependencies, which is why
30 we recommend using semantic versions for dependencies. The error may be fixed by running
34 go get -u github.com/uber/jaeger-client-go/
45 ### Environment variables
47 The tracer can be initialized with values coming from environment variables, if it is
72 JAEGER_TAGS | A comma separated list of `name=value` tracer-level tags, which get added to all repo…
80 variables.
195 * **Shared sampling state**: the sampling state is shared across all local
[all …]
|
| /dports/net-im/dendrite/dendrite-0.5.1/vendor/github.com/uber/jaeger-client-go/ |
| H A D | README.md | 19 and [semantic versioning](http://semver.org/) when including this library into an application.
28 If you instead want to use the latest version in `master`, you can pull it via `go get`.
29 Note that during `go get` you may see build errors due to incompatible dependencies, which is why
30 we recommend using semantic versions for dependencies. The error may be fixed by running
34 go get -u github.com/uber/jaeger-client-go/
45 ### Environment variables
47 The tracer can be initialized with values coming from environment variables, if it is
72 JAEGER_TAGS | A comma separated list of `name=value` tracer-level tags, which get added to all repo…
80 variables.
195 * **Shared sampling state**: the sampling state is shared across all local
[all …]
|
| /dports/net-mgmt/promscale/promscale-0.6.2/vendor/github.com/uber/jaeger-client-go/ |
| H A D | README.md | 19 and [semantic versioning](http://semver.org/) when including this library into an application.
28 If you instead want to use the latest version in `master`, you can pull it via `go get`.
29 Note that during `go get` you may see build errors due to incompatible dependencies, which is why
30 we recommend using semantic versions for dependencies. The error may be fixed by running
34 go get -u github.com/uber/jaeger-client-go/
45 ### Environment variables
47 The tracer can be initialized with values coming from environment variables, if it is
72 JAEGER_TAGS | A comma separated list of `name=value` tracer-level tags, which get added to all repo…
80 variables.
195 * **Shared sampling state**: the sampling state is shared across all local
[all …]
|
| /dports/www/grafana8/grafana-8.3.6/vendor/github.com/uber/jaeger-client-go/ |
| H A D | README.md | 19 and [semantic versioning](http://semver.org/) when including this library into an application.
28 If you instead want to use the latest version in `master`, you can pull it via `go get`.
29 Note that during `go get` you may see build errors due to incompatible dependencies, which is why
30 we recommend using semantic versions for dependencies. The error may be fixed by running
34 go get -u github.com/uber/jaeger-client-go/
45 ### Environment variables
47 The tracer can be initialized with values coming from environment variables, if it is
72 JAEGER_TAGS | A comma separated list of `name=value` tracer-level tags, which get added to all repo…
80 variables.
195 * **Shared sampling state**: the sampling state is shared across all local
[all …]
|
| /dports/www/grafana8/grafana-8.3.6/vendor/github.com/grafana/loki/vendor/github.com/uber/jaeger-client-go/ |
| H A D | README.md | 19 and [semantic versioning](http://semver.org/) when including this library into an application.
28 If you instead want to use the latest version in `master`, you can pull it via `go get`.
29 Note that during `go get` you may see build errors due to incompatible dependencies, which is why
30 we recommend using semantic versions for dependencies. The error may be fixed by running
34 go get -u github.com/uber/jaeger-client-go/
45 ### Environment variables
47 The tracer can be initialized with values coming from environment variables, if it is
72 JAEGER_TAGS | A comma separated list of `name=value` tracer-level tags, which get added to all repo…
80 variables.
195 * **Shared sampling state**: the sampling state is shared across all local
[all …]
|
| /dports/net-mgmt/prometheus2/prometheus-2.30.3/vendor/github.com/uber/jaeger-client-go/ |
| H A D | README.md | 19 and [semantic versioning](http://semver.org/) when including this library into an application.
28 If you instead want to use the latest version in `master`, you can pull it via `go get`.
29 Note that during `go get` you may see build errors due to incompatible dependencies, which is why
30 we recommend using semantic versions for dependencies. The error may be fixed by running
34 go get -u github.com/uber/jaeger-client-go/
45 ### Environment variables
47 The tracer can be initialized with values coming from environment variables, if it is
72 JAEGER_TAGS | A comma separated list of `name=value` tracer-level tags, which get added to all repo…
80 variables.
195 * **Shared sampling state**: the sampling state is shared across all local
[all …]
|