Skip to content

Instantly share code, notes, and snippets.

View pletcher's full-sized avatar

Charles Pletcher pletcher

View GitHub Profile

Keybase proof

I hereby claim:

  • I am pletcher on github.
  • I am pletcher (https://keybase.io/pletcher) on keybase.
  • I have a public key ASBaeueUjGfN2LXYXmQzDC8zhNOOM-8vjHhwwUdtvivlJwo

To claim this, I am signing this object:

@pletcher
pletcher / meson-log.txt
Created January 20, 2019 22:28
Meson build log
Build started at 2019-01-20T17:25:39.082510
Main binary: /usr/bin/python
Python system: Linux
The Meson build system
Version: 0.49.0
Source dir: /home/pletcher/.cache/yay/wlroots-git/src/wlroots-git
Build dir: /home/pletcher/.cache/yay/wlroots-git/src/wlroots-git/build
Build type: native build
WARNING: Unknown options: "xcb-xkb"
Project name: wlroots
@pletcher
pletcher / pletcher_gsoc_cltk.md
Last active August 28, 2017 21:26
CLTK GSoC Work Product

Note about my contributions on GitHub: Because of my previous work at the Flatiron School, I oversaw an enormous number of GitHub repositories. (My commits were attached to thousands of student forks.) As a result, the GitHub UI has tended not to work very well for me/on my profile. As a workaround, GitHub staff disabled showing public commits in my profile; to see my commits, one has to go to each repository that I've worked on individually.

CLTK Frontend

My work on the CLTK Frontend focused on preparing the project to support annotations, but in the process my work also involved a bit of bug-fixing/feature development to the core project so that I could better understand the application's needs and build the annotations library with those needs in mind.

@pletcher
pletcher / aws_mapping.vm
Last active September 10, 2015 20:03
AWS Mapping for consume application/x-www-form-urlencoded and producing application/json (for, e.g., subsequent consumption by an AWS Lambda function)
## Original: https://forums.aws.amazon.com/thread.jspa?messageID=674293
## A lot of people have probably used the original and had it work well
## for them. However, I'm posting this gist to correct a subtle but
## frustrating bug in the original. Jump to the bottom for a comparison.
## convert HTML FORM POST data to JSON for insertion directly into a Lambda function
## get the raw post data from the AWS built-in variable and give it a nicer name
#set($rawPostData = $input.path('$'))