stoffeastrom

ʕ◔ϖ◔ʔ
U+0295, U+25D4, U+03D6, U+25D4, U+0294

stoffeastrom

# README: This allows you to store in your history file only commands
# with a successful status (or forced exited by you with signal 2).
# Put this content in your .zhsrc
# CREDITS: inspired by https://scarff.id.au/blog/2019/zsh-history-conditional-on-command-success/

# This function will be hooked to zshaddhistory.
# zshaddhistory is called before a history line is saved.  See zshmisc(1).
function my_zshaddhistory() {
  # Prevent the command from being written to history before it's
  # executed; save it to LASTHIST instead.  Write it to history

stoffeastrom

Symbols

Usage	Notation
definition	=
concatenation	,
termination	;
alternation	|
optional	[ ... ]
repetition	{ ... }

stoffeastrom

require "formula"
require_relative "lib/private_strategy"

class Hoge < Formula
  homepage "https://github.com/yourcompany/hoge"
  url "https://github.com/yourcompany/hoge/releases/download/v0.1.0/hoge_v0.1.0_darwin_amd64.tar.gz", :using => GitHubPrivateRepositoryReleaseDownloadStrategy
  sha256 "6de411ff3e4b1658a413dd6181fcXXXXXXXXXXXXXXXXXXXX"
  head "https://github.com/yourcompany/hoge.git"
  version "0.1.0"

stoffeastrom

REF: https://stackoverflow.com/a/12681856

Untracked files are stored in the third parent of a stash commit. (This isn't actually documented, but is pretty obvious from The commit which introduced the -u feature, 787513..., and the way the rest of the documentation for git-stash phrases things... or just by doing git log --graph stash@{0})

You can view just the "untracked" portion of the stash via:

git show stash@{0}^3

stoffeastrom

set -e, -u, -o pipefail

The "set" lines These lines deliberately cause your script to fail. Wait, what? Believe me, this is a good thing. With these settings, certain common errors will cause the script to immediately fail, explicitly and loudly. Otherwise, you can get hidden bugs that are discovered only when they blow up in production.

set -euo pipefail is short for:

set -e
set -u

stoffeastrom

• Create an empty folder
• Go into the folder
• Init package
• Install dependencies
• Add babel.config.js
• Add src and test folders
• Add button.js in src folder
• Add button.spec.js in test folder
• Run the tests
• step-by-step-gif

stoffeastrom

collapsible markdown?

CLICK ME

yes, even hidden code blocks!

print("hello world!")

stoffeastrom

#!/usr/bin/env bash

set -x
shopt -s extglob dotglob

cd "$HOME"
rm -rf "$HOME/TEMP_DIR"
mkdir "$HOME/TEMP_DIR"
cd "$HOME/TEMP_DIR"
git init

stoffeastrom

Default

Powerlevel9k