henrik

tmux cheatsheet

As configured in my dotfiles.

start new:

tmux

start new with session name:

davidbella

class Person
  def initialize(attributes)
    attributes.each do |attribute_name, attribute_value|
      ##### Method one #####
      # Works just great, but uses something scary like eval
      # self.class.class_eval {attr_accessor attribute_name}
      # self.instance_variable_set("@#{attribute_name}", attribute_value)

      ##### Method two #####
      # Manually creates methods for both getter and setter and then 

jonathanhle

1) Exit babun.
2) cmd /c %SYSTEMDRIVE%\Users\%USERNAME%\.babun\cygwin\bin\dash.exe -c '/usr/bin/rebaseall -v'

maxrimue

#!/bin/bash

# Assume we have two semantic versions that we want to compare:

version1=0.12.0
version2=1.15.5

# First, we replace the dots by blank spaces, like this:

version1=${version1//./ }

Karreg

#!/bin/bash

echo "WARN: This will remove everything from docker: volumes, containers and images. Will you dare? [y/N] "
read choice

if [ \( "$choice" == "y" \) -o \( "$choice" == "Y" \) ]
then
  sudo echo "> sudo rights [OK]"
  sizea=`sudo du -sh /var/lib/docker/aufs`

ireade

self.addEventListener('install', (e) => {
    e.waitUntil(
        caches.open("precache").then((cache) => cache.add("/broken.png"))
    );
});

function isImage(fetchRequest) {
    return fetchRequest.method === "GET" && fetchRequest.destination === "image";
}

StevenACoffman

Set GOPRIVATE to match your github organization

I keep fixing this up, but if it fails for you, check if these are better maintained https://tip.golang.org/cmd/go/#hdr-Configuration_for_downloading_non_public_code and https://golang.org/ref/mod#private-modules.

Cloning the repo using one of the below techniques should work correctly but you may still be getting an unrecognized import error.

As it stands for Go v1.13, I found in the doc that we should use the GOPRIVATE variable like so:

GOPRIVATE=github.com/ORGANISATION_OR_USER_NAME go get -u -f github.com/ORGANISATION_OR_USER_NAME/REPO_NAME

The 'go env -w' command (see 'go help env') can be used to set these variables for future go command invocations.

candlerb

If someone asked me the question "what layout should I use for my Go code repository?", I'd start by asking back "what are you building: an executable, or a library?"

Single executable

Stage 1: single source file

Create a directory named however you want your final executable to be called (e.g. "mycommand"), change into that directory, and create the following files: