| /dports/print/texlive-base/texlive-20150521-source/utils/asymptote/ |
| H A D | runhistory.in | 17 using namespace camp;
18 using namespace settings;
19 using namespace vm;
20 using namespace run;
23 using types::stringArray;
27 #include <readline/history.h>
131 store_history(&history);
142 stringarray* history(Int n=0)
152 // Prompt for a string using prompt, the GNU readline library, and a
153 // local history named name.
[all …]
|
| /dports/math/asymptote/asymptote-2.67/ |
| H A D | runhistory.in | 17 using namespace camp;
18 using namespace settings;
19 using namespace vm;
20 using namespace run;
23 using types::stringArray;
27 #include <readline/history.h>
131 store_history(&history);
142 stringarray* history(Int n=0)
152 // Prompt for a string using prompt, the GNU readline library, and a
153 // local history named name.
[all …]
|
| /dports/www/py-django-simple-history/django-simple-history-2.12.0/docs/ |
| H A D | multiple_dbs.rst | 7 `django-simple-history` follows the Django conventions for interacting with multiple databases.
12 >>> poll = Poll.objects.using('other').create(question='Question 1')
15 >>> poll.save(using='other')
18 When interacting with ``QuerySets``, use ``using()``:
23 Poll.history.using('other').all()
30 >>> poll.history.db_manager('other').as_of(datetime(2010, 10, 25, 18, 4, 0))
37 When using ``django-simple-history`` in app with multiple database, you may run into
38 an issue where you want to track the history on a table that lives in a separate
40 you will have to manually track the ``history_user`` using an explicit ID. The full
45 You can choose whether or not to track models' history in the same database by
[all …]
|
| H A D | querying_history.rst | 4 Querying history on a model instance
16 >>> poll.history.all()
25 >>> poll.history.all()
28 Querying history on a model class
31 Historical records for all instances of a model can be queried by using the
33 records for all ``Choice`` instances can be queried by using the manager on the
41 >>> Choice.history
43 >>> Choice.history.all()
116 model history.
149 Filtering data using a relationship to the model
[all …]
|
| /dports/www/py-django-simple-history/django-simple-history-2.12.0/django_simple_history.egg-info/ |
| H A D | PKG-INFO | 2 Name: django-simple-history
86 - Exclude ManyToManyFields when using ``bulk_create_with_history`` (gh-699)
130 - Fix ``model_to_dict`` to detect changes in a parent model when using
132 using previous version) (gh-576)
159 - Fixed bug that prevented self-referential foreign key from using ``'self'`` (gh-513)
164 \* NOTE: This change was not backward compatible for users using routers to write
185 - Fix bug that caused failures when using a custom user model (gh-459)
292 - Allow setting a reason for change. [using option changeReason]
296 - Fix migrations while using ``order_with_respsect_to`` (gh-140)
297 - Fix migrations using south
[all …]
|
| /dports/www/py-django-simple-history/django-simple-history-2.12.0/ |
| H A D | PKG-INFO | 2 Name: django-simple-history
86 - Exclude ManyToManyFields when using ``bulk_create_with_history`` (gh-699)
130 - Fix ``model_to_dict`` to detect changes in a parent model when using
132 using previous version) (gh-576)
159 - Fixed bug that prevented self-referential foreign key from using ``'self'`` (gh-513)
164 \* NOTE: This change was not backward compatible for users using routers to write
185 - Fix bug that caused failures when using a custom user model (gh-459)
292 - Allow setting a reason for change. [using option changeReason]
296 - Fix migrations while using ``order_with_respsect_to`` (gh-140)
297 - Fix migrations using south
[all …]
|
| H A D | CHANGES.rst | 10 - Exclude ManyToManyFields when using ``bulk_create_with_history`` (gh-699)
42 - import model ``ContentType`` in ``SimpleHistoryAdmin`` using ``django_apps.get_model``
54 - Fix ``model_to_dict`` to detect changes in a parent model when using
56 using previous version) (gh-576)
74 - Fix hardcoded history manager (gh-542)
88 \* NOTE: This change was not backward compatible for users using routers to write
109 - Fix bug that caused failures when using a custom user model (gh-459)
216 - Allow setting a reason for change. [using option changeReason]
220 - Fix migrations while using ``order_with_respsect_to`` (gh-140)
221 - Fix migrations using south
[all …]
|
| /dports/textproc/texi2html/texi2html-5.0/test/manuals/res_all/ccvs_mediawiki_nosplit/ |
| H A D | cvs: history--Show status of files and users | 1 <div id="history"></div>
4 …xt: [[cvs: import--Import sources into CVS, using vendor branches#import—Import sources into…
10 === history—Show status of files and users ===
11 <div id="index-history-_0028subcommand_0029"></div>
16 * Requires: the file ‘<tt>$CVSROOT/CVSROOT/history</tt>’
20 <small>CVS</small> can keep a history file that tracks each use of the
23 use <code>history</code> to display this information in
27 ‘<tt>$CVSROOT/CVSROOT/history</tt>’.
29 '''Note: <code>history</code> uses ‘<code>-f</code>’, ‘<code>-l</code>’,
33 [[cvs: history options#history options|• history options]]:: history options
[all …]
|
| H A D | cvs: The history database | 1 <div id="history-database"></div>
9 <div id="The-history-database"></div>
10 === The history database ===
12 You can use the history file (see [[cvs: The history file#The history file|history file]]) to
14 information from the history file, use the <code>cvs
15 history</code> command (see [[cvs: history--Show status of files and users#history—Show statu…
17 Note: you can control what is logged to this file by using the
22 This document was generated on <i>a sunny day</i> using [http://www.nongnu.org/texi2html/ <i>texi2h…
|
| /dports/textproc/texi2html/texi2html-5.0/test/manuals/res_info/ccvs_mediawiki_nosplit/ |
| H A D | cvs: history--Show status of files and users | 1 <div id="history"></div>
4 …xt: [[cvs: import--Import sources into CVS, using vendor branches#import—Import sources into…
10 === history—Show status of files and users ===
11 <div id="index-history-_0028subcommand_0029"></div>
16 * Requires: the file ‘<tt>$CVSROOT/CVSROOT/history</tt>’
20 <small>CVS</small> can keep a history file that tracks each use of the
23 use <code>history</code> to display this information in
27 ‘<tt>$CVSROOT/CVSROOT/history</tt>’.
29 '''Note: <code>history</code> uses ‘<code>-f</code>’, ‘<code>-l</code>’,
33 [[cvs: history options#history options|• history options]]:: history options
[all …]
|
| H A D | cvs: The history database | 1 <div id="history-database"></div>
9 <div id="The-history-database"></div>
10 === The history database ===
12 You can use the history file (see [[cvs: The history file#The history file|history file]]) to
14 information from the history file, use the <code>cvs
15 history</code> command (see [[cvs: history--Show status of files and users#history—Show statu…
17 Note: you can control what is logged to this file by using the
22 This document was generated on <i>a sunny day</i> using [http://www.nongnu.org/texi2html/ <i>texi2h…
|
| /dports/devel/gitlab-runner/gitlab-runner-8925d9a06fd8e452e2161a768462652a2a13111f/vendor/github.com/docker/cli/cli-20.10.2/docs/reference/commandline/ |
| H A D | history.md | 2 title: "history"
4 keywords: "docker, image, history"
7 # history chapter
10 Usage: docker history [OPTIONS] IMAGE
12 Show the history of an image
15 --format string Pretty-print images using a Go template
28 $ docker history docker
42 $ docker history docker:scm
53 using a Go template.
66 When using the `--format` option, the `history` command will either
[all …]
|
| /dports/sysutils/helm/helm-3.5.2/vendor/github.com/docker/cli/docs/reference/commandline/ |
| H A D | history.md | 2 title: "history"
4 keywords: "docker, image, history"
7 # history chapter
10 Usage: docker history [OPTIONS] IMAGE
12 Show the history of an image
15 --format string Pretty-print images using a Go template
28 $ docker history docker
42 $ docker history docker:scm
53 using a Go template.
66 When using the `--format` option, the `history` command will either
[all …]
|
| /dports/net-im/twirssi/twirssi-2579820/html/ |
| H A D | index.php | 88 $about = $installing = $using = $history = ""; variable
93 $using = "id=\"selected\""; variable
96 $history = "id=\"selected\""; variable
110 <li <?=$using?>><a href="?using">Using</a></li>
111 <li <?=$history?>><a href="?history">Version History</a></li>
|
| /dports/textproc/kibana7/kibana-7.16.2-darwin-x86_64/node_modules/history/ |
| H A D | README.md | 19 // using ES6 modules
22 // using CommonJS modules
99 - `history.length` - The number of entries in the history stack
107 You can listen for changes to the current location using `history.listen`:
133 When you attach a listener using `history.listen`, it returns a function that can be used to remove…
143 `history` objects may be used to programmatically change the current location using the following m…
147 - `history.go(n)`
152 When using `push` or `replace` you can either specify both the URL path and state as separate argum…
167 history.push({
175 history.go(-1);
[all …]
|
| H A D | CHANGES.md | 69 - Allow relative pathnames in `history.push` and `history.replace` ([#135])
77 - Fixed `createLocation` defaults when using objects instead of strings
107 - Added `history.length`, `history.location`, and `history.action` properties
108 - Added `history.index` and `history.entries` properties in memory history
121 - Better warnings for PUSH with the same path using hash history
132 - Switched to using `window.history.state` in `createBrowserHistory` instead of `sessionStorage`.
199 the location has state. This obsoletes using `{ queryKey: false }` to prevent
203 opt-out of using it entirely by not using location state
269 - Deprecate the `query` arg to `createPath` and `createHref` in favor of using location descriptor …
277 - Accept objects in `history.push` and `history.replace` ([#141])
[all …]
|
| /dports/textproc/opensearch-dashboards/opensearch-dashboards-1.2.0-linux-x64/node_modules/history/ |
| H A D | README.md | 19 // using ES6 modules
22 // using CommonJS modules
99 - `history.length` - The number of entries in the history stack
107 You can listen for changes to the current location using `history.listen`:
133 When you attach a listener using `history.listen`, it returns a function that can be used to remove…
143 `history` objects may be used to programmatically change the current location using the following m…
147 - `history.go(n)`
152 When using `push` or `replace` you can either specify both the URL path and state as separate argum…
167 history.push({
175 history.go(-1);
[all …]
|
| H A D | CHANGES.md | 69 - Allow relative pathnames in `history.push` and `history.replace` ([#135])
77 - Fixed `createLocation` defaults when using objects instead of strings
107 - Added `history.length`, `history.location`, and `history.action` properties
108 - Added `history.index` and `history.entries` properties in memory history
121 - Better warnings for PUSH with the same path using hash history
132 - Switched to using `window.history.state` in `createBrowserHistory` instead of `sessionStorage`.
199 the location has state. This obsoletes using `{ queryKey: false }` to prevent
203 opt-out of using it entirely by not using location state
269 - Deprecate the `query` arg to `createPath` and `createHref` in favor of using location descriptor …
277 - Accept objects in `history.push` and `history.replace` ([#141])
[all …]
|
| /dports/sysutils/docker/docker-ce-18.09.5/components/cli/docs/reference/commandline/ |
| H A D | history.md | 2 title: "history"
4 keywords: "docker, image, history"
16 # history chapter
19 Usage: docker history [OPTIONS] IMAGE
21 Show the history of an image
24 --format string Pretty-print images using a Go template
37 $ docker history docker
51 $ docker history docker:scm
62 using a Go template.
75 When using the `--format` option, the `history` command will either
[all …]
|
| /dports/www/chromium-legacy/chromium-88.0.4324.182/chrome/browser/federated_learning/ |
| H A D | floc_id_provider_impl.h | 50 public history::HistoryServiceObserver,
77 using CanComputeFlocCallback = base::OnceCallback<void(bool)>;
78 using ComputeFlocCompletedCallback =
80 using GetRecentlyVisitedURLsCallback =
81 history::HistoryService::QueryHistoryCallback;
87 history::HistoryService* history_service,
115 void OnURLsDeleted(history::HistoryService* history_service,
116 const history::DeletionInfo& deletion_info) override;
141 history::QueryResults results);
177 history::HistoryService* history_service_;
|
| /dports/shells/fish/fish-3.3.1/tests/checks/ |
| H A D | history.fish | 4 # First using the legacy, now deprecated, long options to specify a
8 history --search --merge
10 history --clear --contains
12 history --merge -t
14 history --save xyz
27 # Now using the preferred subcommand form. Note that we support flags before
31 history clear --contains
33 history merge -t
35 history save xyz
37 history --prefix clear
[all …]
|
| /dports/shells/ohmyzsh/ohmyzsh-6babcbd8841335a3c25ec960ff57ab9a139c9073/plugins/per-directory-history/ |
| H A D | README.md | 1 per-directory-history plugin
4 This plugin adds per-directory history for zsh, as well as a global history,
8 To use it, add `per-directory-history` to the plugins array in your zshrc file:
11 plugins=(... per-directory-history)
15 of which exist in bash[1][],[2][]. It also implements a toggle-history function
16 to change from using the directory history to using the global history. In both
17 cases the history is always saved to both the global history and the directory
23 The default mode is per directory history, interact with your history as normal.
33 * `per-directory-history-toggle-history` is the function to toggle between local
44 [1]: http://www.compbiome.com/2010/07/bash-per-directory-bash-history.html
[all …]
|
| /dports/net-im/telegram-desktop/tdesktop-3.2.5-full/Telegram/SourceFiles/data/ |
| H A D | data_sponsored_messages.h | 27 History *history = nullptr; member
33 using RandomId = QByteArray;
39 [[nodiscard]] bool canHaveFor(not_null<History*> history) const;
40 void request(not_null<History*> history);
41 [[nodiscard]] bool append(not_null<History*> history);
42 void clearItems(not_null<History*> history);
48 using OwnedItem = std::unique_ptr<HistoryItem, HistoryItem::Destroyer>;
64 not_null<History*> history,
67 not_null<History*> history,
|
| /dports/databases/postgresql96-server/postgresql-9.6.24/src/interfaces/ecpg/test/expected/ |
| H A D | compat_informix-test_informix2.stderr | 7 [NO_PID]: ecpg_execute on line 66: using PQexec
13 [NO_PID]: ecpg_execute on line 68: using PQexec
19 [NO_PID]: ecpg_execute on line 71: using PQexec
23 [NO_PID]: ecpg_execute on line 76: query: select max ( timestamp ) from history; with 0 parameter(s…
25 [NO_PID]: ecpg_execute on line 76: using PQexec
31 [NO_PID]: ecpg_execute on line 81: query: select customerid , timestamp from history where timestam…
33 [NO_PID]: ecpg_execute on line 81: using PQexecParams
43 [NO_PID]: ecpg_execute on line 95: query: insert into history ( customerid , timestamp , action_tak…
45 [NO_PID]: ecpg_execute on line 95: using PQexecParams
55 [NO_PID]: ecpg_execute on line 102: query: drop table history; with 0 parameter(s) on connection ec…
[all …]
|
| /dports/databases/postgresql96-pltcl/postgresql-9.6.24/src/interfaces/ecpg/test/expected/ |
| H A D | compat_informix-test_informix2.stderr | 7 [NO_PID]: ecpg_execute on line 66: using PQexec
13 [NO_PID]: ecpg_execute on line 68: using PQexec
19 [NO_PID]: ecpg_execute on line 71: using PQexec
23 [NO_PID]: ecpg_execute on line 76: query: select max ( timestamp ) from history; with 0 parameter(s…
25 [NO_PID]: ecpg_execute on line 76: using PQexec
31 [NO_PID]: ecpg_execute on line 81: query: select customerid , timestamp from history where timestam…
33 [NO_PID]: ecpg_execute on line 81: using PQexecParams
43 [NO_PID]: ecpg_execute on line 95: query: insert into history ( customerid , timestamp , action_tak…
45 [NO_PID]: ecpg_execute on line 95: using PQexecParams
55 [NO_PID]: ecpg_execute on line 102: query: drop table history; with 0 parameter(s) on connection ec…
[all …]
|