Add the following chunk to your existing ISC dhcpd.conf file.
if exists user-class and ( option user-class = "iPXE" ) {
filename "http://boot.smidsrod.lan/boot.ipxe";
}
else {
filename "undionly.kpxe";
}
(or see https://gist.github.com/4008017 for a more elaborate setup
| # Install `dnsmasq` and configure for *.dev domains | |
| $ brew install dnsmasq | |
| $ vim /usr/local/etc/dnsmasq.conf | |
| # Reload configuration and clear cache | |
| $ sudo launchctl unload /Library/LaunchDaemons/homebrew.mxcl.dnsmasq.plist | |
| $ sudo launchctl load /Library/LaunchDaemons/homebrew.mxcl.dnsmasq.plist | |
| $ dscacheutil -flushcache |
| # to generate your dhparam.pem file, run in the terminal | |
| openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048 |
This is a full set of key bindings (as of Vimium v1.45); covering all Vimium functionality. I have tried to map all Vimium functionality to comparable Emacs functionality (whenever possible). In cases where there is no equivalent, those commands are prefixed by <c-g> (indicating <c-g>oogle Chrome; and because <c-g> does not conflict with other Emacs shortcuts at all).
Commented Shortcuts: There are a few Emacs-style shortcuts that are simply not possible in Vimium. All of my shortcuts (including those which were not possible; i.e. where I used a decent alternative) have been commented below. This should help to clarify my rationale.
_Compatibility: All of these shortcuts were tested on Mac OS X (Mavericks). Please note that all of my shortcuts operate under the assumption that your Emacs Meta key is the ⌥ Alt/Option key. This really was my only choice, because the ⌘ key is already used in Chrome for shortcuts that c
| (ns mk.fe.core.why-update | |
| (:require [cljsjs.react])) | |
| (defn comp-did-update [prev-props prev-state] | |
| (this-as this | |
| (let [name (or (aget this "displayName") | |
| (aget this "constructor" "displayName") | |
| (aget this "constructor" "name")) | |
| prev-state (aget prev-state ":rum/state") | |
| state (aget (.-state this) ":rum/state")] |
A note on terminology: There are a lot of things with similar meanings/use-cases around: subscriptions, reactions, derived atoms, view models.
I'll introduce another to make things even worse: derivative. A derivative implements IWatchable and it's value is the result of applying a function to the value of other things (sources) implementing IWatchable. Whenever any of the sources change the value if the derivative is updated.
Let's assume you're hooked about the idea of storing all your application state in a single atom (db). (Why this is a great idea is covered elsewhere.)
Most of your components don't need the entirety of this state and instead receive a small selection of it that is enough to allow the components to do their job. Now that data is not always a subtree (i.e. (get-in db ...)) but might be a combination of various parts of your state. To transform the data in a way that it becomes useful for components you can use a function: `(f @
| (ns myapp.core (:gen-class)) | |
| (gen-class | |
| :name myapp.Application | |
| :extends javafx.application.Application | |
| :prefix "myapp-") | |
| (defn ^:Private myapp-start | |
| "Implements javafx.application.Application.start." | |
| [app ^javafx.stage.Stage stage] |
| ------------------------------------------------------------------- | |
| --Hammerspoon config to replace Cinch & Size-up (Microsoft Windows style) window management for free | |
| --By Jayden Pearse (spartanatreyu) | |
| --Sort of messy, forgive me. Never scripted in lua before | |
| ------------------------------------------------------------------- | |
| ------------------------------------------------------------------- | |
| --Options, feel free to edit these | |
| ------------------------------------------------------------------- |
After my dad died, I wanted to be able to have access any of his online accounts going forward. My dad was a Safari user and used iCloud Keychain to sync his credentials across his devices. I don’t want to have to keep an OS X user account around just to access his accounts, so I wanted to export his credentials to a portable file.
This is the process I used to create a CSV file of his credentials in the format “example.com,user,pass”. This portable format would be pretty easy to import into 1Password or Safari in the future.
The way I went about this isn’t great; it opens up more opportunities for apps to control one’s Mac through Accessibility APIs, it writes plaintext passwords to disk, and it could use some cleaning up. A better approach might leverage the security command line tool that ships with OS X. That said, I found this method to be a fun illustration of what’s possible us