ryuheechul

package collection

# Map

my_add(x, y) = x + y

map_add[x] = val {
	col := input.col
	delta := input.delta

ryuheechul

My note below is based on https://gist.github.com/readywater/49a9fbc415141aeb02d2f1e15e643f70 but modifed it to make it work for me in 15th Aug 2021, Remarkable 2 version 2.8.0.98.

Install package manager via Toltec

the official installation instruction is here, https://toltec-dev.org/#install-toltec

# SSH into the remarkable
ssh root@

ryuheechul

progm + [hotkey] Changes Layouts

• progrm + m => m_querty.txt (macOS)
• progrm + w => w_querty.txt (Windows)

progm + <Esc> Prints Status

Make sure to open a editor that your keyboard can print (type) it out.

Advantages 2 Support Page

https://kinesis-ergo.com/support/advantage2

ryuheechul

// a quick memory leak tester

// TODO: actually verify and make it objectively testable

function getRandomInt(max: number) {
  return Math.floor(Math.random() * max);
}

const size = 2000 * 1000 as const; // whatever length to make the size big enough at each step

ryuheechul

But why? At least three reasons:

1. You want to use local images without having to push to a remote registry

• you probably just built an image locally and want to use that image with a helm chart
• you can see the image when you run minikube image ls
• but you still got an error on image pulling and the reason was imagePullPolicy: Always

2. with imagePullPolicy: Always, minikube (or probably limitation on k8s) will always attempt to pull from remote registry ignoring "locally pulled" ones

• see more on that at https://minikube.sigs.k8s.io/docs/handbook/pushing/#3-pushing-directly-to-in-cluster-cri-o-podman-env
• and https://kubernetes.io/docs/concepts/containers/images/#image-pull-policy
• and https://kubernetes.io/docs/concepts/containers/images/#pre-pulled-images

3. Helm charts not always expose imagePullPolicy as editable values

ryuheechul

How Nix works

Nix is a purely functional package manager

/nix folder in my dotfiles repo

this is how I utilize nix to have better management of initial setup in terms of both logically and performantely better

How I package Docker image using Nix

My first attempt to package with Nix for a Docker image with Dockerfile

From Homebrew to Home Manager

ryuheechul

Context about Emacs and me

I used a few text editors (with vim key bindings) lightly for a number of years and I started wanting more.

In 2016, I first stumbled upon Spacemacs and got hooked for a while. That was my first Emacs experience. Spacemacs was so user friendly that I didn't have to learn Emacs at all.

In 2017, I moved on to VSCode (with VSpaceCode) as it got popular. In 2019, I moved to [Neo]vim (with SpaceVim) mainly because of the better performance and it was a natural transition as I also started using Tmux and I started to refuse leaving terminals.

ryuheechul

bootstrap

• nix: https://github.com/NixOS/nixpkgs
• homebrew: https://brew.sh/
• fluid: https://fluidapp.com/
  • https://www.noisli.com/

(almost) mouseless

• alfred4: https://www.alfredapp.com/
• keytty: https://keytty.com/
• amethyst: https://ianyh.com/amethyst/

ryuheechul

# vim: set ft=zsh:

## You are suppose to source this file from your shell - tested on zsh and might work with bash as well
# like `source [this_file]`
# You can turn this into scripts if that's more of your taste

## binary dependancies
# - https://github.com/stedolan/jq           # json processor
# - https://github.com/charmbracelet/glow    # markdown render on cli
# - https://github.com/httpie/httpie         # A command line HTTP client whose goal is to make CLI human-friendly

ryuheechul

#!/usr/bin/env bash

url='https://github.com' # or whatever url you want to check
sec=3

while true; do
	date -u +%H:%M:%S # or date +%H:%M:%S
	echo "${url}"
	# https://unix.stackexchange.com/a/84820/396504
	curl -Is "${url}" | head -n 1 && sleep "${sec}"