calendarID from cal.csv can be used at path param in
https://developers.google.com/calendar/v3/reference/calendars/get
https://developers.google.com/calendar/v3/reference/events/list
| #! /bin/bash | |
| n=32 | |
| arg=setaf | |
| text='Hello World! This is %s %d' | |
| _help() | |
| { | |
| printf 'usage: %s [--help|-H] [--16] [--256] [-t|--tiny] [--background|-b]\n' "$(basename $0)" | |
| exit 0 |
- import project into idea command
$ curl -L "https://gist.githubusercontent.com/chrisdarroch/7018927/raw/9a6d663fd7a52aa76a943fe8a9bc6091ad06b18d/idea" -o /usr/local/bin/idea
$ chmod +x /usr/local/bin/idea
- unzip and open project command
$ curl -L "https://gist.githubusercontent.com/sgyyz/adfa4f05af3d81cf0e17e19cf7044c85/raw/b6b9e871d5a4f5435a09d00b0a52e3db0b90699a/uao.sh" -o /usr/local/bin/uao.sh
$ chmod +x /usr/local/bin/uao.sh
$ ln -sf /usr/local/bin/uao.sh /usr/local/bin/uao
| #!/usr/bin/expect | |
| set username "mstiborsky\r" | |
| set config "/etc/openvpn/client/zonky.conf" | |
| set vpn_oauth_token [exec ykman oath code -s vpn] | |
| spawn openvpn --config $config --auth-user-pass | |
| expect "Enter Auth Username:" | |
| send $username | |
| expect "Enter Auth Password:" |
| #!/bin/bash -e | |
| if [ $# -ne 2 ]; then | |
| echo "Usage: $0 <instance-id> <volume-size-gb> [PARITION_NAME=/dev/xvda2]" | |
| exit 2 | |
| fi | |
| INSTANCE="$1" | |
| VOLUME_SIZE="$2" | |
| PARTITION="${3:-/dev/xvda2}" |
React recently introduced an experimental profiler API. After discussing this API with several teams at Facebook, one common piece of feedback was that the performance information would be more useful if it could be associated with the events that caused the application to render (e.g. button click, XHR response). Tracing these events (or "interactions") would enable more powerful tooling to be built around the timing information, capable of answering questions like "What caused this really slow commit?" or "How long does it typically take for this interaction to update the DOM?".
With version 16.4.3, React added experimental support for this tracing by way of a new NPM package, scheduler. However the public API for this package is not yet finalized and will likely change with upcoming minor releases, so it should be used with caution.
| import kotlinx.coroutines.experimental.* | |
| import kotlinx.coroutines.experimental.channels.ReceiveChannel | |
| import kotlinx.coroutines.experimental.channels.consumeEach | |
| import kotlinx.coroutines.experimental.channels.produce | |
| import kotlin.coroutines.experimental.CoroutineContext | |
| fun <E> ReceiveChannel<E>.debounce( | |
| wait: Long = 50, | |
| context: CoroutineContext = DefaultDispatcher | |
| ): ReceiveChannel<E> = produce(context) { |
| <script type="text/javascript"> | |
| var demoPartner = { 'host': '#HOST#', 'projectId': #PROJECT_ID#, 'template': '#TEMPLATE#' }; | |
| </script> | |
| <script src="https://cdn.myshoptet.com/usr/demo-partner.myshoptet.com/user/documents/addon_1/common.js" type="text/javascript"></script> | |
| <link href="https://cdn.myshoptet.com/usr/demo-partner.myshoptet.com/user/documents/addon_1/#TEMPLATE#.css" rel="stylesheet" /> | |
| <link href="https://cdn.myshoptet.com/usr/demo-partner.myshoptet.com/user/documents/addon_1/#HOST#/style.css?v=1" rel="stylesheet" /> |