daveio

Use mise.

If you're not using mise as your version manager, you really should consider it.

It's become my primary way of installing things, only falling back to Homebrew when absolutely necessary.

Combined with chezmoi this keeps my tooling in sync across every environment I work in.

Shims

jdx

# this is an example "usage" definition
# it defines a subset of the tool "rtx". What syntax it uses for CLI arguments
# as well as how it interacts with env vars and config files
# usage can be thought of as "swagger for CLIs"
# The purpose is that having a language-agnostic definition for CLIs we can
# build tools like generic autocompletion (so you don't need to learn how to write complex bash/zsh completions)
# It would also allow us to build documentation tools (browser or CLI), scaffold out CLIs, and build
# parsing/validation libraries to make CLI development faster.

# CLI parsing starts here. This is close, but probably not identical to docopt.

jdx

#!/bin/bash
set -euxo pipefail

# Downloads a node tarball from https://nodejs.org/dist/ and extracts just
# the binary into the current directory. Chiefly we use this to get a node
# binary for uploading to manifold.

if [[ $# -ne 4 ]]; then
  echo "USAGE: $0 <node_version> <os> <arch> <filename>"
  exit 1

jdx

--- Actions ---
$Copy                                              <M-C>
$Cut                                               <M-X> <S-Del>
$Delete                                            <Del> <BS> <M-BS>
$LRU
$Paste                                             <M-V>
$Redo                                              <M-S-Z> <A-S-BS>
$SearchWeb
$SelectAll                                         <M-A>
$Undo                                              <M-Z>

jdx

'use strict';

let http  = require('http');
let https = require('https');
let parseUrl = require('url').parse;

function concat (stream, callback) {
  var strings = [];
  stream.on('data', function (data) {
    strings.push(data);

17twenty

a simple git branching model

This is a very simple git workflow. It (and variants) is in use by many people. I settled on it after using it very effectively at Athena. GitHub does something similar; Zach Holman mentioned it in this talk.

The gist

fgrehm

if ! $(psql template1 -c 'SHOW SERVER_ENCODING' | grep -q UTF8); then
  psql postgres -c "update pg_database set datallowconn = TRUE where datname = 'template0';"
  psql template0 -c "update pg_database set datistemplate = FALSE where datname = 'template1';"
  psql template0 -c "drop database template1;"
  psql template0 -c "create database template1 with template = template0 encoding = 'UTF8';"
  psql template0 -c "update pg_database set datistemplate = TRUE where datname = 'template1';"
  psql template1 -c "update pg_database set datallowconn = FALSE where datname = 'template0';"
fi

jdx

# Example:
#
# dickeyxxx@dickey-mbp ~/proj/tapjoykc 1.9.3-p194 (routes ✔)
# ✗✗✗ 

if [[ $TERM = *256color* || $TERM = *rxvt* ]]; then
  turquoise="%F{81}"
  orange="%F{166}"
  purple="%F{135}"
  hotpink="%F{161}"

geemus

TODO empty arrays and/or nil values (see apps:info)

General Guidelines

• Use full sentences, including punctuation.
• Labels should be provided where needed in the form of 'Labels labels:'.
• Commands should have one newline between the header and body and another after the body.
• Alpha-sort arrays before display and display labeled data in alpha-sorted key order.