| --Hammerspoon config to replace Cinch & Size-up (Microsoft Windows style) window management for free | |
| --Windows Vista/7's Areo Snap on MacOS | |
| --By Jayden Pearse (spartanatreyu) | |
| ------------------------------------------------------------------- | |
| --Options, feel free to edit these: | |
| ------------------------------------------------------------------- | |
| --Set this to true to snap windows by dragging them to the edge of your screen | |
| enable_window_snapping_with_mouse = true |
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
https://gist.github.com/ljharb/58faf1cfcb4e6808f74aae4ef7944cff
While attempting to explain JavaScript's reduce method on arrays, conceptually, I came up with the following - hopefully it's helpful; happy to tweak it if anyone has suggestions.
JavaScript Arrays have lots of built in methods on their prototype. Some of them mutate - ie, they change the underlying array in-place. Luckily, most of them do not - they instead return an entirely distinct array. Since arrays are conceptually a contiguous list of items, it helps code clarity and maintainability a lot to be able to operate on them in a "functional" way. (I'll also insist on referring to an array as a "list" - although in some languages, List is a native data type, in JS and this post, I'm referring to the concept. Everywhere I use the word "list" you can assume I'm talking about a JS Array) This means, to perform a single operation on the list as a whole ("atomically"), and to return a new list - thus making it mu
| LShift & Capslock:: | |
| SetCapsLockState, % (State:=!State) ? "on" : "alwaysoff" | |
| Return | |
| g_AbortSendEsc := false | |
| #InstallKeybdHook | |
| SetCapsLockState, alwaysoff | |
| Capslock:: | |
| g_DoNotAbortSendEsc := true |
| ''' | |
| vitafunctiondefs.py by xerpi | |
| arm-vita-eabi-gcc -E $VITASDK/arm-vita-eabi/include/vitasdk.h -D"__attribute__(x)=" -D"__extension__(x)=" > preprocessor_user.h | |
| arm-vita-eabi-gcc -E $VITASDK/arm-vita-eabi/include/vitasdkkern.h -D"__attribute__(x)=" -D"__extension__(x)=" > preprocessor_kern.h | |
| ''' | |
| import sys | |
| import os.path | |
| import struct |
This was created years ago; at the time I'd been a Shibboleth admin for nearly a decade but we needed something that could handle OIDC/OAuth and that explicitly supported OpenJDK. After a lot of investigation, I really liked Keycloak/Red Hat Single Sign-On. More details here: Gluu vs keycloack vs wso2 identity management
(Items in bold indicate possible concerns)
| import argparse | |
| import json | |
| import os | |
| import posixpath | |
| import shutil | |
| import subprocess | |
| import tempfile | |
| import requests |
When I use docker to work with the shared workspace with host under Ubuntu, I find that files created by docker user is owned by root. This is not the same with macOS.
Maybe this is becuase docker is run by root user and the default user mapping mechanism is to map container-root to host-user or host-root. So can I map the container-root or container-any-user to host-current-user?
Fortunately the latest docker supports the re-map the container user to any host user via Linux namespace. Refer to this.
/opt)
ℹ️ Enable iCloud end-to-end encryption:
System settings → Apple ID → iCloud → Set Advanced Data Protection to On.System settings → Apple ID → iCloud → Disable Access iCloud Data on the Web.