Jakub Beneš jukben

tig - Text-mode interface for git

This is a proposal for #ReactiveConf 2017 open call for Lightning talks.

Do you think that using git command line tool is the most efficient way of interacting with your repository? In this lightning talk, I will introduce tig - the ncurses front-end for git, which will make your interaction with git much more efficient.

tig combines the advantages of the command line and GUI tools like qgit. With a couple of keystrokes, you are

Bridging Native & React for iOS & Android

js -> native

native -> js

RxJS 5 Operators By Example

⚠️ UPDATE: I have moved the contents of this gist plus more to http://www.learnrxjs.io and https://github.com/btroncone/learn-rxjs. For expanded examples, explanations, and resources, please check out this new location!

A complete list of RxJS 5 operators with easy to understand explanations and runnable examples.

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.

Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.

Element APIs

Getting box metrics

elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent

	#!/usr/bin/env bash

	# Brew
	echo "Installing 🍺 Brew!"
	/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
	echo "eval $(/opt/homebrew/bin/brew shellenv)" >> ~/.zshrc


	# Disable brew analytics
	brew analytics off

	# Pass the env-vars to MYCOMMAND
	eval $(egrep -v '^#' .env \| xargs) MYCOMMAND
	# … or ...
	# Export the vars in .env into your shell:
	export $(egrep -v '^#' .env \| xargs)

	{
	"extends": [
	"@frontend/coinbase",
	"prettier",
	"prettier/react",
	"prettier/flowtype"
	],
	"rules": {
	"flowtype/type-id-match": [
	2,

	Community Packages (43) /home/capaj/.atom/packages
	├── [email protected]
	├── [email protected]
	├── [email protected]
	├── [email protected]
	├── [email protected]
	├── [email protected]
	├── [email protected]
	├── [email protected]
	├── [email protected]

	# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
	# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
	# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
	# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

	# Add the following to your shell init to set up gpg-agent automatically for every shell
	if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
	source ~/.gnupg/.gpg-agent-info
	export GPG_AGENT_INFO
	else