- Set Light mode
defaults write -g NSRequiresAquaSystemAppearance -bool Yes
- Log out and log back in
- Set Dark mode
#!/bin/bash | |
set -e | |
CONTENTS=$(tesseract -c language_model_penalty_non_dict_word=0.8 --tessdata-dir /usr/local/share/tessdata/ "$1" stdout -l eng | xml esc) | |
hex=$((cat <<EOF | |
<?xml version="1.0" encoding="UTF-8"?> | |
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> | |
<plist version="1.0"> |
// direct_uploads.js
addEventListener("direct-upload:initialize", event => {
const { target, detail } = event
const { id, file } = detail
license:gpl-3.0 | |
height:680 | |
border:no |
BC.registerElement "bc-require", | |
createdCallback: -> | |
@setAttribute("pending", "") | |
attachedCallback: -> | |
BC.ready => | |
if Loader.find(@script)?.loaded | |
@activate() | |
else | |
@deactivate() |
#!/bin/sh | |
defaults read com.apple.finder CreateDesktop > /dev/null 2>&1 | |
enabled=$? | |
if [ "$1" = "off" ]; then | |
if [ $enabled -eq 1 ]; then | |
defaults write com.apple.finder CreateDesktop false | |
osascript -e 'tell application "Finder" to quit' | |
open -a Finder |
addEventListener "trix-initialize", (event) -> | |
new TrixAutoLinker event.target | |
class TrixAutoLinker | |
constructor: (@element) -> | |
{@editor} = @element | |
@element.addEventListener("trix-render", @autoLink) | |
@autoLink() | |
autoLink: => |
Several years ago I got curious about how css worked at scale. When I first started out, there weren’t nearly as many learning resources as there are now. CSS zen garden was amazing, at the time it showed how much you could change a design without altering the html.
In the beginning, that’s what people sold me as a feature. By writing css, you could make a change one place and have it propagate everywhere. In principle this sounds pretty good. I’m lazy so I like doing things one time. But eleven years later, my experience on both large and small teams is that this is the most terrifying thing about css.
https://twitter.com/thomasfuchs/status/493790680397803521
In the past few years a lot of very smart people have been thinking more about CSS and this has lead to some fascinating discussions around how to build ‘scalable’ ui and how that relates to CSS. When I first started to think about scalability I naturally started to read every blog post and watch every tech talk I could get
module RichTextHelper | |
cattr_accessor(:id, instance_accessor: false) { 0 } | |
def rich_text_field_tag(name, value = nil, options = {}) | |
options.symbolize_keys! | |
attributes = { | |
class: "formatted_content #{options[:class]}".squish | |
} |
Thanks for contacting AppleCare chat support. My name is Buddy. Please give me a moment to look over your information.
Buddy: Well hey there Daniel!
Before we get started, I wanted to ask how you're doing?
That way you'll know I'm not a robot, although being a robot would be pretty cool!
Me: Hah, I’m doing pretty good thanks. How're you?