| /dports/editors/emacs-devel/emacs-4d1968b/doc/misc/ |
| H A D | remember.texi | 209 Here is one way to map the remember functions in your init file
221 set @code{remember-run-all-annotation-functions-flag} to a
224 @defopt remember-run-all-annotation-functions-flag
226 @code{remember-annotation-functions}.
230 remember-annotation-functions. For example:
236 (let ((remember-annotation-functions '(buffer-file-name)))
254 @file{remember.el} defines the following interactive functions:
349 (setq remember-handler-functions '(remember-append-to-file))
370 (setq remember-handler-functions '(remember-store-in-files))
393 (add-to-list 'remember-handler-functions 'remember-diary-extract-entries)
[all …]
|
| /dports/editors/emacs/emacs-27.2/doc/misc/ |
| H A D | remember.texi | 208 Here is one way to map the remember functions in your init file
220 set @code{remember-run-all-annotation-functions-flag} to a
223 @defopt remember-run-all-annotation-functions-flag
225 @code{remember-annotation-functions}.
229 remember-annotation-functions. For example:
235 (let ((remember-annotation-functions '(buffer-file-name)))
253 @file{remember.el} defines the following interactive functions:
348 (setq remember-handler-functions '(remember-append-to-file))
369 (setq remember-handler-functions '(remember-store-in-files))
392 (add-to-list 'remember-handler-functions 'remember-diary-extract-entries)
[all …]
|
| /dports/www/elgg/elgg-3.3.23/vendor/elgg/elgg/docs/guides/ |
| H A D | authentication.rst | 7 * remember-me cookies for persistent login
14 the built-in authentication functions to secure your pages and actions.
50 Gatekeeper functions allow you to manage how code gets executed by applying access control rules.
73 …ss an authentication request. This involves setting up an authentication handler in the plugin's :…
75 …handler is a function and takes a single parameter. Registering the handler is being done by ``reg…
80 // Register the authentication handler
101 …handler can vary, depending on the originating request. For example, a regular login via the login…
106 …er will get logged in. In case of the XML-RPC example the authentication handler will need to perf…
|
| /dports/print/pslib/pslib-0.4.6/doc/ |
| H A D | PS_new2.sgml | 13 Please remember that if you create the nroff version in one of the
71 handler and memory management functions. If you pass NULL values the
72 internal default handler and functions will be used. In such case you
|
| /dports/shells/zsh/zsh-5.8.1/Functions/TCP/ |
| H A D | tcp_close | 7 # Accepts the -s and -l arguments for consistency with other functions,
61 # to a pre-existing fd. We could remember this from tcp_open.
93 if (( ${+functions[tcp_on_unalias]} )); then
101 # Don't return just because the zle handler couldn't be uninstalled...
129 if (( ${+functions[tcp_on_close]} )); then
|
| /dports/databases/pxlib/pxlib-0.6.8/doc/ |
| H A D | PX_new3.sgml | 13 Please remember that if you create the nroff version in one of the
71 must be called before any other functions. If the caller has its own
72 error and memory management functions they can be passed.</para>
75 user data which is passed to the error handler function as the
78 to passed to the error handler through a global variable.</para>
|
| /dports/math/py-pygsl/pygsl-2.3.0/ |
| H A D | ChangeLog | 6 * Modified the pygsl error handler:
7 If PyGSL does not set gsl_error handler to off, the installed error
8 handler will now store the arguments passed by gsl_error_handler to a
18 functions releasing the GIL (e.g UFUNC's).
71 Before I installed a gsl_error handler. This handler would then
72 translate the error numbers to python exceptions. Now this handler
103 * What did I do the last years? I do not remember ....
109 * input1 was used as second input in functions
142 generic functions.
155 This changed the API for many functions
[all …]
|
| /dports/lang/librep/librep_0.92.7/lisp/rep/vm/compiler/ |
| H A D | utils.jl | 38 remember-function forget-function
39 remember-variable
40 remember-lexical-variable
70 ; for all functions/macros in the file
198 (defun remember-variable (name)
207 (defun remember-lexical-variable (name)
242 ;; XXX functions in comp-fun-bindings aren't type-checked
262 (remember-function name (nth 1 decl)))
377 (let ((handler (get (or (car clause) clause) 'compiler-decl-fun)))
378 (if handler
[all …]
|
| H A D | rep.jl | 39 ;; List of side-effect-free functions. They should always return the
41 (define constant-functions
257 ;; tells the constant-folder which functions can be removed
259 (memq name constant-functions))
278 (remember-variable name)
789 ;; Loop over all but the last handler
809 "badly formed condition-case handler: `%s'"
812 ;; The last handler
830 "badly formed condition-case handler: `%s'"
849 ;; unbind ;unbind error handler or VAR
[all …]
|
| /dports/net/rabbitmq/rabbitmq-server-3.9.11/deps/systemd/ |
| H A D | README.md | 18 - `journal` logger handler and formatters.
43 This application and all functions within are safe to call even in non-systemd
45 all functions will simply work as (almost) no-ops.
217 This handler **should not** be used with `systemd_kmsg_formatter` as this will
220 You can also "manually" configgure handler if you want to configure formatter:
239 1. Disable Elixir's backends and just rely on default Erlang's handler:
250 2. "Manually" add handler that will use `systemd_kmsg_formatter`:
261 However remember, that currently (as Elixir 1.11) there is no "Elixir formatter"
275 Or you can manually configure the handler:
292 This handler **should not** be used with `:systemd_kmsg_formatter` as this will
|
| /dports/devel/tla/tla-1.3.5/src/docs-hackerlab/texi/ |
| H A D | vu.texi | 227 vtable as the handler for the new descriptor.
231 top of stack down. Each handler has a name and an array of
252 fd = handler->vtable->open (errn, path, flags, mode,
253 handler->closure);
280 For each VU namespace handler and file-descriptor handler, there
374 @code{name} is the name for the handler recognized by
428 Push the named namespace handler on the VU namespace stack.
431 The named handler must have previously been established by a
456 The handler is automatically removed by @code{vu_close}.
471 Move the VU handler for @code{fd} to @code{newfd}.
[all …]
|
| /dports/audio/py-fmoo-audiotools/audiotools-3.0/src/decoders/ |
| H A D | NOTES.rst | 9 with lots of little pieces to remember.
23 ``PyGetSetDef`` functions include:
30 While ``PyMethodDef`` functions include:
116 All our other functions can simply return ``Py_None``.
194 static helper functions.
206 that a failed read can ``longjmp`` back up to the error handler -
209 since jumping back to an error handler won't give one a chance
|
| /dports/net/samba412/samba-4.12.15/lib/tevent/doc/ |
| H A D | tevent_thread.dox | 68 out of the basic functions and isolation mechanisms of tevent,
69 but tevent also comes with some utility functions that make
98 tevent_immediate_handler_t handler,
103 This function causes the function <code>handler()</code>
124 <code>handler()</code> will be called as a normal tevent_immediate
128 Returning from this functions does not mean that the <code>handler</code>
135 confirmation of the <code>handler()</code> being
152 <code>handler</code> is called.
318 But remember the caveat that external synchronization must be used
|
| /dports/devel/tevent/tevent-0.10.2/doc/ |
| H A D | tevent_thread.dox | 68 out of the basic functions and isolation mechanisms of tevent,
69 but tevent also comes with some utility functions that make
98 tevent_immediate_handler_t handler,
103 This function causes the function <code>handler()</code>
124 <code>handler()</code> will be called as a normal tevent_immediate
128 Returning from this functions does not mean that the <code>handler</code>
135 confirmation of the <code>handler()</code> being
152 <code>handler</code> is called.
318 But remember the caveat that external synchronization must be used
|
| /dports/databases/ldb15/ldb-1.5.6/lib/tevent/doc/ |
| H A D | tevent_thread.dox | 68 out of the basic functions and isolation mechanisms of tevent,
69 but tevent also comes with some utility functions that make
98 tevent_immediate_handler_t handler,
103 This function causes the function <code>handler()</code>
124 <code>handler()</code> will be called as a normal tevent_immediate
128 Returning from this functions does not mean that the <code>handler</code>
135 confirmation of the <code>handler()</code> being
152 <code>handler</code> is called.
318 But remember the caveat that external synchronization must be used
|
| /dports/databases/ldb20/ldb-2.0.10/lib/tevent/doc/ |
| H A D | tevent_thread.dox | 68 out of the basic functions and isolation mechanisms of tevent,
69 but tevent also comes with some utility functions that make
98 tevent_immediate_handler_t handler,
103 This function causes the function <code>handler()</code>
124 <code>handler()</code> will be called as a normal tevent_immediate
128 Returning from this functions does not mean that the <code>handler</code>
135 confirmation of the <code>handler()</code> being
152 <code>handler</code> is called.
318 But remember the caveat that external synchronization must be used
|
| /dports/databases/ldb21/ldb-2.1.5/lib/tevent/doc/ |
| H A D | tevent_thread.dox | 68 out of the basic functions and isolation mechanisms of tevent,
69 but tevent also comes with some utility functions that make
98 tevent_immediate_handler_t handler,
103 This function causes the function <code>handler()</code>
124 <code>handler()</code> will be called as a normal tevent_immediate
128 Returning from this functions does not mean that the <code>handler</code>
135 confirmation of the <code>handler()</code> being
152 <code>handler</code> is called.
318 But remember the caveat that external synchronization must be used
|
| /dports/databases/ldb22/ldb-2.2.1/lib/tevent/doc/ |
| H A D | tevent_thread.dox | 68 out of the basic functions and isolation mechanisms of tevent,
69 but tevent also comes with some utility functions that make
98 tevent_immediate_handler_t handler,
103 This function causes the function <code>handler()</code>
124 <code>handler()</code> will be called as a normal tevent_immediate
128 Returning from this functions does not mean that the <code>handler</code>
135 confirmation of the <code>handler()</code> being
152 <code>handler</code> is called.
318 But remember the caveat that external synchronization must be used
|
| /dports/net/boinc-client/boinc-client_release-7.8-7.8.6/drupal/sites/default/boinc/modules/contrib/views/handlers/ |
| H A D | views_handler_filter.inc | 85 * or to at least make sure all of the functions in this form
102 * Simple validate handler
114 * Simple submit handler
356 $form['expose']['remember'] = array(
360 '#default_value' => $this->options['expose']['remember'],
379 form_error($form['expose']['identifier'], t('This identifier is used by another handler.'));
398 'remember' => FALSE,
557 if (empty($this->options['expose']['remember'])) {
611 * A special handler to take the place of missing or broken handlers.
615 return t('Broken/missing handler');
[all …]
|
| /dports/textproc/R-cran-XML/XML/man/ |
| H A D | xmlEventParse.Rd | 12 invoking user-level functions associated with different
39 also provide handler functions for specific tags/elements such
55 So the key thing to remember about dealing with text is that the
57 to the text handler. A common idiom is to have the text handler
109 Support for connections and functions in this form is only
178 list of handler functions whose name matches (exactly) the name of
182 functions can write node-specific handlers for the different element
184 these functions within the \code{startElement} function. This is done
220 callback where again it will be updated by that functions return
260 \item{branches}{a named list of functions.
[all …]
|
| /dports/irc/libircclient/libircclient-1.10/doc/sources/ |
| H A D | Appendix_FAQ.rst | 61 …time later the IRC server returns an error. This is because the irc_cmd family of functions return
109 The built-in handler reacts on TIME, VERSION, PING and FINGER CTCP queries. If you need to react on…
110 you’ll have to write your own CTCP handler. See the source code of libirc_event_ctcp_internal funct…
130 …* Extract the descriptors from the fd_set arrays (remember fd_array is a bitarray, not the value a…
132 … the events, fill up the relevant in_set and out_set structures (again, remember the bitmasks!) an…
|
| /dports/devel/ode/ode-0.13/ode/ |
| H A D | README | 37 3x1 vector arguments to set() functions are supplied as x,y,z.
55 there are helper functions which allocate objects out of areans, in case you
60 a better approach is to supply custom memory allocation functions
133 * remember to compile resources to COFF format RES files.
140 to plug in your own collision handling, replace (some of?) these functions
147 linked in? e.g. only one space handler, and sphere-sphere and sphere-box and
155 there should be utility functions which create the dynamics and collision
|
| /dports/www/mod_perl2/mod_perl-2.0.11/todo/ |
| H A D | bugs_mp | 59 the coincidence that both the response handler and the filter were
61 where push_handlers() uses a string as a handler, rather a CODE
82 1) enforce that these functions are used only at the server startup
88 [remember that Apache::warn is needed for registry scripts to
|
| /dports/x11-toolkits/py-wxPython40/wxPython-4.0.7/docs/sphinx/rest_substitutions/overviews/ |
| H A D | events_overview.rst | 65 - A handler method in the same or another object.
111 objects, including simple functions).
115 event handler::
177 how the next handler may be defined.
227 dialogs that may be popped up in a complex program (remember that some
257 handler in the event handler chain. This chain can be formed using
314 self.Bind(EVT_SOME_NEW_EVENT, self.handler)
315 EVT_SOME_NEW_EVENT(self, self.handler)
333 def handler(self, evt):
351 (e.g., resize of a :ref:`wx.Window`) and by calls to functions (e.g.,
[all …]
|
| /dports/devel/p5-POE-Quickie/POE-Quickie-0.18/ |
| H A D | README | 18 Context => 'remember this',
25 Context => 'remember this',
54 event handler and gives control back to POE while your task is running,
56 "quickie_*" functions which are exported by default.
163 Blocking functions
164 The following functions are modeled after the ones provided by
172 Note: Since these functions block, you must be careful not to call them
|