| return function(INPUT_LINE_NUMBER, CURSOR_LINE, CURSOR_COLUMN) | |
| print('kitty sent:', INPUT_LINE_NUMBER, CURSOR_LINE, CURSOR_COLUMN) | |
| vim.opt.encoding='utf-8' | |
| vim.opt.clipboard = 'unnamed' | |
| vim.opt.compatible = false | |
| vim.opt.number = false | |
| vim.opt.relativenumber = false | |
| vim.opt.termguicolors = true | |
| vim.opt.showmode = false | |
| vim.opt.ruler = false |
| #!/usr/bin/env bash | |
| pid=$(pgrep gammastep) | |
| if [[ $1 = "toggle" ]]; then | |
| if pgrep -x "gammastep" > /dev/null; then | |
| kill -9 $(pgrep -x "gammastep"); | |
| else | |
| gammastep -O ${GAMMASTEP_NIGHT:-3500} & | |
| fi |
Here are my working notes on getting a system up and running.
WARNING: You can run into a hidden problem that will prevent a correct partition setup and /etc/nixos/configuration.nix from working: if you are setting up a UEFI system, then you need to make sure you boot into the NixOS installation from the UEFI partition of the bootable media. You may have to enter your BIOS boot selection menu to verify this. For example, if you setup a NixOS installer image on a flash drive, your BIOS menu may display several boot options from that flash drive: choose the one explicitly labeled with “UEFI”.
I used these resources:
https://www.buildfunthings.com/linux/ https://gist.github.com/OctavioBR/5992416015d73253e92929d9c8be8cb4 https://gist.github.com/gilbertw1/81ef4b0bcf3ddefa4b18 https://wiki.archlinux.org/index.php/Installation_guide https://wiki.archlinux.org/index.php/Mac https://linustechtips.com/main/topic/575993-guide-installing-arch-linux-on-a-vmware-virtual-machine/
| # /usr/share/BasiliskII/keycodes | |
| # | |
| # Basilisk II (C) 1997-2005 Christian Bauer | |
| # | |
| # This file is used to translate the (server-specific) scancodes to | |
| # Mac keycodes depending on the window server being used. | |
| # | |
| # The format of this file is as follows: | |
| # | |
| # sdl <driver string> |
NOTE: This is no longer an experiment! You can use the accessibility inspector in Chrome Devtools now, including a fantastic color contrast inspection tool. Read more: https://developers.google.com/web/updates/2018/01/devtools#a11y
Just like any good element inspector helps you debug styles, accessibility inspection in the browser can help you debug HTML and ARIA exposed for assistive technologies such as screen readers. There's a similar tool in Safari (and reportedly one in Edge) but I like the Chrome one best.
As an internal Chrome experiment, this tool differs from the Accessibility Developer Tools extension in that it has privileged Accessibility API access and reports more information as a result. You can still use the audit feature in the Chrome Accessibility Developer Tools, or you could use the aXe Chrome extension. :)
To enable the accessibility inspector in Chrome stable:
This table was created in 2015 so may be quite outdated today.
| Feature | Meteor Solution | Alternative Solutions | Description |
|---|---|---|---|
| Live DB Sync | [livequery][lq] ([mongo-oplog]), [ddp] | RethinkDB, Redis, ShareDB, [npm:mongo-oplog], [firebase], etc. | Push DB updates to client/server. |
| Latency Compensation, Optimistic UI | [minimongo][mm] | [RethinkDB][lcr], [mWater/minimongo] (fork, not ws but http, browserify) | Imitate successful db query on client before it is done. |
| Isomorphic Code | [isobuild] & isopacks | browserify | Write one code for server/client/mobile. |
| Isomorphic Packaging | [isobuild], atmosphere | No more separate packages for server & client. Get bower + npm + mobile. |