A list of useful commands for the FFmpeg command line tool.
Download FFmpeg: https://www.ffmpeg.org/download.html
Full documentation: https://www.ffmpeg.org/ffmpeg.html
| ;; # EMULATING DATOMIC EXCISION VIA MANUAL DATA MIGRATION | |
| ;; ************************************* | |
| ;; ## Introduction | |
| ;; ************************************* | |
| ;; This Gist demonstrates a generic way to migrate an entire Datomic database | |
| ;; from an existing 'Origin Connection' to a clean 'Destination Connection', | |
| ;; while getting rid of some undesirable data and otherwise preserving history. |
| global | |
| log 127.0.0.1 local0 notice | |
| maxconn 4096 | |
| user haproxy | |
| group haproxy | |
| ssl-server-verify none | |
| defaults | |
| log global | |
| mode http |
A list of useful commands for the FFmpeg command line tool.
Download FFmpeg: https://www.ffmpeg.org/download.html
Full documentation: https://www.ffmpeg.org/ffmpeg.html
To me, "require-and-automatically-visible" is violating the beauty of namespace. But, maybe I felt this way because I don't understand Clojure's registry or how require works.
I thought about this more, and I think I have a better understanding of why this feels strange. Clojure has one thing called "namespaces" which are clojure.lang.Namespace objects created by the ns macro. Functionally speaking they are a storage location which mostly just contain vars and references to vars in other namespaces. They are used for code organization: specifically for organizing vars and occasionally Java classes and interfaces.
Clojure also has a completely different thing called "namespaces" which are prefixes that get attached to keywords and symbols. These can interact with ns namespaces thru the reader in a handful of ways (for instance, ::double-colon keywords and symbols inside backtick forms are resolved according to the current clojure.lang.Namespace) but for the most part should be considered a di
| (function() { | |
| 'use strict'; | |
| // keep track of all the opened tab | |
| let tabs = {}; | |
| // Get all existing tabs | |
| chrome.tabs.query({}, function(results) { | |
| results.forEach(function(tab) { | |
| tabs[tab.id] = tab; |
pg_dump is a nifty utility designed to output a series of SQL statements that describes the schema and data of your database. You can control what goes into your backup by using additional flags.
Backup: pg_dump -h localhost -p 5432 -U postgres -d mydb > backup.sql
Restore: psql -h localhost -p 5432 -U postgres -d mydb < backup.sql
-h is for host.
-p is for port.
-U is for username.
-d is for database.
| #ifndef RANGE_HPP_ | |
| #define RANGE_HPP_ | |
| template<typename T> class RangeIterator; | |
| template<typename T> | |
| class Range | |
| { | |
| T _start, _end, _step; |
| // MIT Licensed | |
| // Author: jwilson8767 | |
| /** | |
| * Waits for an element satisfying selector to exist, then resolves promise with the element. | |
| * Useful for resolving race conditions. | |
| * | |
| * @param selector | |
| * @returns {Promise} | |
| */ |
| ------------------------- MODULE GryadkaCasRegister ------------------------- | |
| EXTENDS Integers, Sequences, FiniteSets | |
| ----------------------------------------------------------------------------- | |
| \* Timestamps is the set of possible timestamps for operations to choose from. | |
| \* Each operation uses a unique timestamp. | |
| \* Values is the set of possible values to set the register to. | |
| \* Acceptors is the set of nodes which act as acceptors in the paxos sense. | |
| \* Quorums is the set of all possible quorums, typically simple majorities. | |
| CONSTANTS Timestamps, Values, Acceptors, Quorums |