Standard escape codes are prefixed with Escape
:
- Ctrl-Key:
^[
- Octal:
\033
- Unicode:
\u001b
- Hexadecimal:
\x1B
- Decimal:
27
Credits go to https://docs.docker.com/registry/recipes/nginx/ and http://mindtrove.info/control-read-write-access-docker-private-registry/
Follow the steps on https://docs.docker.com/registry/recipes/nginx/ with docker-compose.yml and nginx.conf below.
Run the following for admin UI:
docker run \
#!/bin/sh | |
if [ $# -eq 0 ]; then | |
echo "Usage: $0 <new_ip_address>" | |
exit 1 | |
fi | |
socat udp4-listen:8889,fork,reuseaddr,bind=$1 udp:192.168.10.1:8889 |
/* | |
Source: https://github.com/raywenderlich/swift-algorithm-club/tree/dd1ed39fca150d4fa2905b902736f12a49f3efb1/Ring%20Buffer | |
Fixed-length ring buffer | |
In this implementation, the read and write pointers always increment and | |
never wrap around. On a 64-bit platform that should not get you into trouble | |
any time soon. | |
Not thread-safe, so don't read and write from different threads at the same | |
time! To make this thread-safe for one reader and one writer, it should be | |
enough to change read/writeIndex += 1 to OSAtomicIncrement64(), but I haven't |
\documentclass{your_thesis_class} | |
\usepackage[utf8x]{inputenc} % <--- required by Inkscape generated pdf_tex figures. biblatex won't work with these | |
\usepackage[numbers]{natbib} | |
% \setcitestyle{numbers} % <--- if natbib is already included by another package | |
\usepackage{bibunits} % <--- lets you have a separate bibliography, e.g. your own publications list | |
\begin{document} | |
\begin{bibunit}[unsrtnat] % <--- unsrtnat arranges bibliography list in appearance order |
You can't use bridging headers within a framework.
Xcode will automatically create umbrella header for you Cocoa Framework project. That will be the file named <FrameworkName>.h
in the <FrameworkName>
group/folder (where the rest of your sources are).
Public
: select it in the project explorer (left pane) and change the property Target Membership
(left—Inspectors—pane) from Project
to Public
.<FrameworkName>.h
) and import the required header as:FROM HUE DESIGN DOCS
#Conversion between RGB and xy in the CIE 1931 colorspace for hue The conversion between RGB and xy in the CIE 1931 colorspace is not something Philips invented, but we have an optimized conversion for our different light types, like hue bulbs and LivingColors. It is important to differentiate between the various light types, because they do not all support the same color gamut. For example, the hue bulbs are very good at showing nice whites, while the LivingColors are generally a bit better at colors, like green and cyan.
[ | |
{ | |
"class": "title_bar", | |
"fg": ["background", 255, 255, 255, 0.7], | |
// "bg": ["background", 63, 65, 72, 1.0] | |
}, | |
{ | |
"class": "title_bar", | |
"attributes": ["file_dark"], | |
"bg": ["background", 255, 255, 255, 0.15] |