All notable changes to this configuration will be documented in this file.
- Enhanced Git integration
- Pull command:
<leader>g p
- Pull command:
- Push command:
g P
" Vim syntax file | |
" Language: Todo | |
" Maintainer: Huy Tran | |
" Latest Revision: 14 June 2020 | |
if exists("b:current_syntax") | |
finish | |
endif | |
" Custom conceal |
An easy to refer to document for regularly setting up macOS 10.13 High Siera, in flavor of my previous macOS/OSX setup gists:
I use this gist to keep track of the important software and steps required to have a functioning system after a semi-annual fresh install. I generally reinstall each computer from scratch every 6 months, and I do not perform upgrades between releases.
Past August 2024, Authy stopped supported the desktop version of their apps:
See Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August for details.
And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export your tokens.
If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.
import AWS from 'aws-sdk'; | |
const lambda = new AWS.Lambda(); | |
const createAsyncInvokeParams = ( | |
{ | |
functionName, | |
payload | |
} | |
) => ({ |
Name | Version | License | URL |
---|---|---|---|
align-text | 0.1.4 | MIT | git://github.com/jonschlinkert/align-text.git |
amdefine | 1.0.0 | BSD-3-Clause AND MIT | https://github.com/jrburke/amdefine.git |
async | 1.5.2 | MIT | https://github.com/caolan/async.git |
async | 0.2.10 | MIT | https://github.com/caolan/async.git |
balanced-match | 0.4.2 | MIT | git://github.com/juliangruber/balanced-match.git |
brace-expansion | 1.1.6 | MIT | git://github.com/juliangruber/brace-expansion.git |
camelcase | 1.2.1 | MIT |
server { | |
listen 80; | |
server_name ip.domain.tld; | |
add_header Content-Type text/plain; | |
return 200 $remote_addr; | |
} |
<?xml version="1.0"?> | |
<!DOCTYPE fontconfig SYSTEM "fonts.dtd"> | |
<fontconfig> | |
<alias> | |
<family>sans-serif</family> | |
<prefer> | |
<family>NotoSans</family> | |
<family>NotoColorEmoji</family> | |
<family>NotoEmoji</family> | |
</prefer> |
Last Updated: March 2023
IMPORTANT: Ignore the out-of-date steps below for getting Chromium keys.
Instead, read this up-to-date guide (Jan 2023) written by @LearningToPi.
P.S. Thank you to every contributor below who provided tips over the years on what should be a straightforward process: setting up Chromium for local development.
Long live the web!