rodricels

# My tmux configuration, partly based on https://github.com/wbkang/wbk-stow/blob/master/tmux-config/.tmux.conf

# Scroll History
set -g history-limit 50000

# show messages for 4 seconds instead
set -g display-time 4000

# set first window to index 1 (not 0) to map more to the keyboard layout
set-option -g renumber-windows on

tzmartin

1. Copy m3u8 link

2. Run command

echo "Enter m3u8 link:";read link;echo "Enter output filename:";read filename;ffmpeg -i "$link" -bsf:a aac_adtstoasc -vcodec copy -c copy -crf 50 $filename.mp4

LeCoupa

# Redis Cheatsheet
# All the commands you need to know


redis-server /path/redis.conf  # start redis with the related configuration file
redis-cli                      # opens a redis prompt


# Strings.

ericclemmons

Using <details> in GitHub

Suppose you're opening an issue and there's a lot noisey logs that may be useful.

Rather than wrecking readability, wrap it in a <details> tag!

<details>
 Summary Goes Here

josephspurrier

package main

import (
	"bufio"
	"io/ioutil"
	"os/signal"
	//"syscall"
	"fmt"
	"log"
	"os"

clemtibs

Commit Message Format

This specification is inspired by and supersedes the [AngularJS commit message format][commit-message-format].

We have very precise rules over how our Git commit messages must be formatted. This format leads to easier to read commit history.

Each commit message consists of a header, a body, and a footer.

lilliemarck

/**
 * Regex for validating a URI or URI Reference as defined in RFC3986.
 *
 * A URI Reference is a URI without the scheme part. They are otherwise the
 * same except that the first segment of a relative path of a URI reference
 * can't contain a ':'.
 *
 * This syntax does not have IPv6 address support and does not include the IPv4
 * rule because IPv4 addresses happens to be a subset of registered names.
 * Although the final regex can be made a little bit more compact the intent is