Sean Marquez capsulecorplab

Emacs packages, features, files, layers, extensions, auto-loading, require, provide, use-package… All these terms getting you confused? Let’s clear up a few things.

Files

Emacs files contains code that can be evaluated. When evaluated, the functions, macros and modes defined in that file become available to the current Emacs session. Henceforth, this will be termed as loading a file.

One major problem is to ensure that all the correct files are loaded, and in the

Alternatives to the "Atlassian Stack"

Fuller stack alternatives (replaces at least two of the Atlassian stack)

Get Git log in JSON format

git log --pretty=format:'{%n  "commit": "%H",%n  "abbreviated_commit": "%h",%n  "tree": "%T",%n  "abbreviated_tree": "%t",%n  "parent": "%P",%n  "abbreviated_parent": "%p",%n  "refs": "%D",%n  "encoding": "%e",%n  "subject": "%s",%n  "sanitized_subject_line": "%f",%n  "body": "%b",%n  "commit_notes": "%N",%n  "verification_flag": "%G?",%n  "signer": "%GS",%n  "signer_key": "%GK",%n  "author": {%n    "name": "%aN",%n    "email": "%aE",%n    "date": "%aD"%n  },%n  "commiter": {%n    "name": "%cN",%n    "email": "%cE",%n    "date": "%cD"%n  }%n},'

The only information that aren't fetched are:

%B: raw body (unwrapped subject and body)
%GG: raw verification message from GPG for a signed commit

Asciidoc cheatsheet for GitHub

EDIT from 2019: Hi folks. I wrote this gist for myself and some friends, and it seems like it's gotten posted somewhere that's generated some (ahem, heated) discussion. ~~The whitespace was correct when it was posted, and since then GitHub changed how it formats <pre> tags. Look at the raw text if you care about this. I'm sure someone could tell me how to fix it, but~~ (thank you @anzdaddy for suggesting a formatting workaround) honestly this is a random throwaway gist from 2015, and someone more knowledgable about this comparison should just write a proper blog post about it. If you comment here I'll hopefully see it and stick a link to it up here. Cheers. @oconnor663

Here's the canonical TOML example from the TOML README, and a YAML version of the same.

title = "TOML Example"

Rails Girls LA 2016 Part 1 Rails 5

	language: ruby
	rvm:
	- 2.0.0
	env:
	global:
	- USER="username"
	- EMAIL="username@mail.com"
	- REPO="name of target repo"
	- FILES="README.md foo.txt bar.txt"
	- GH_REPO="github.com/${USER}/${REPO}.git"

	// ring with cutout
	// default values are for 1mm height, 10mm outside diameter and 5mm cutout
	// de is epsilon environment to make cutouts non-manifold
	module ring(
	h=1,
	od = 10,
	id = 5,
	de = 0.1
	)
	{

	Driver:
	-Write the code according to the navigator's specification
	-Listen intently to the navigators instructions
	-Ask questions wherever there is a lack of clarity
	-Offer alternative solutions if you disagree with the navigator
	-Where there is disagreement, defer to the navigator. If their idea fails, get to failure quickly and move on
	-Make sure code is clean
	-Own the computer / keyboard
	-Ignore larger issues and focus on the task at hand
	-Trust the navigator - ultimately the navigator has the final say in what is written

	sudo apt-get update
	sudo apt-get install python-pip python-dev ipython

	sudo apt-get install bluetooth libbluetooth-dev
	sudo pip install pybluez