jeffmhubbard

local gears = require("gears")
local awful = require("awful")
require("awful.autofocus")
local beautiful = require("beautiful")
local menubar = require("menubar")

beautiful.init(gears.filesystem.get_themes_dir() .. "gtk/theme.lua")

local terminal = "xterm"
local modkey = "Mod4"

jeffmhubbard

local awful = require("awful")

-- Mod keys
superkey = "Mod4"
altkey = "Mod1"
ctrlkey = "Control"
shiftkey = "Shift"

awful.keyboard.append_global_keybindings({
    awful.key({ superkey }, "F2",

jeffmhubbard

# Maintainer: Oleg Shparber <trollixx+aur@gmail.com>
# Contributor: Bartłomiej Piotrowski <bpiotrowski@archlinux.org>
# Contributor: Andrea Scarpino <andrea@archlinux.org>
# Contributor: Sébastien Luttringer
# Contributor: xduugu
# Contributor: Ronald van Haren <ronald.archlinux.org>
# Contributor: Vesa Kaihlavirta
# URL: https://github.com/trollixx/aur-packages
# Upstream: https://projects.archlinux.org/svntogit/community.git/tree/trunk?h=packages/awesome

jeffmhubbard

# Maintainer: Luca CPZ <luca.cpz [at] gmail [dot] com>
# Contributor: Jeff M. Hubbard <jeffmhubbard@gmail.com>
_pkgname=awesome-freedesktop
pkgname=${_pkgname}-git
pkgver=r109.b77dee0
pkgrel=1
pkgdesc="Freedesktop.org compliant desktop entries and menu for Awesome WM"
arch=("any")
url="https://github.com/lcpz/$_pkgname"
license=("GPL2")

jeffmhubbard

#!/usr/bin/env zsh

script=$0
chroot=/mnt

function stage1 {
  # prepare disks and pacstrap...
  script2=${script:t}
  install -Dm755 $script $chroot/$script2
  arch-chroot $chroot /$script2 --chroot

jeffmhubbard

# curl -sG "http://localhost:9999/get_listen_now" \
#   --data-urlencode "format=m3u" \
#   --data-urlencode "type=artist" \
#   >> ~/playlist-current.log;

#EXTM3U
#EXTINF:-1,C I V I L W A R
http://10.0.0.10:9999/get_listen_now_list?id=Br7looridevvs3qhuv6pzodtodm&format=m3u
#EXTINF:-1,Light It Up
http://10.0.0.10:9999/get_listen_now_list?id=Bj62efsp5jzvdx2rhweo6irflce&format=m3u

jeffmhubbard

# Paths {{{
set folder            = ~/Mail                # mailbox location
set alias_file        = ~/.mutt/alias          # where to store aliases
set header_cache      = ~/.mutt/cache/headers  # where to store headers
set message_cachedir  = ~/.mutt/cache/bodies   # where to store bodies
set certificate_file  = ~/.mutt/cerficates     # where to store certs
set mailcap_path      = ~/.mutt/mailcap        # entries for filetypes
set tmpdir            = ~/.mutt/temp           # where to keep temp files
set signature         = ~/.mutt/sig            # my signature file

jeffmhubbard

# populate $WALL_LIST depending on number of displays and images passed
get_wall_list() {

	local paths=("$@")
	declare -ga WALL_LIST

	# multiple images and spanning conflict, bail out
	if [ "${#paths[@]}" -gt 1 ] && [ "$span_image" = true ]; then
		echo "ERROR: can't use --span with multiple images"
		exit 1

jeffmhubbard

Pull Request Etiquette

Why do we use a Pull Request workflow?

PRs are a great way of sharing information, and can help us be aware of the changes that are occuring in our codebase. They are also an excellent way of getting peer review on the work that we do, without the cost of working in direct pairs.

Ultimately though, the primary reason we use PRs is to encourage quality in the commits that are made to our code repositories

Done well, the commits (and their attached messages) contained within tell a story to people examining the code at a later date. If we are not careful to ensure the quality of these commits, we silently lose this ability.

jeffmhubbard

Storing Images and Demos in your Repo

In this quick walkthough you'll learn how to create a separate branch in your repo to house your screenshots and demo gifs for use in your master's readme.

How to

1. Clone a fresh copy of your repo

In order to prevent any loss of work it is best to clone the repo in a separate location to complete this task.

2. Create a new branch

Create a new branch in your repo by using git checkout --orphan assets