sscotth

/**
 * React Static Boilerplate
 * https://github.com/koistya/react-static-boilerplate
 *
 * Copyright © 2015-2016 Konstantin Tarkus (@koistya)
 *
 * This source code is licensed under the MIT license found in the
 * LICENSE.txt file in the root directory of this source tree.
 */

brucemcpherson

<gistThat info="this is a manifest for gistThat VBA code distribution  - see ramblings.mcpher.com for details">
    <manifest description="cDataset and associated classes and modules" contact="bruce@mcpher.com">
        <gists>
            <item1 gistid="3414216" version="" filename="cCell.cls" module="cCell" type="class" />
            <item2 gistid="3414216" version="" filename="cDataSet.cls" module="cDataSet" type="class" />
            <item3 gistid="3414216" version="" filename="cDataSets.cls" module="cDataSets" type="class" />
            <item4 gistid="3414216" version="" filename="cDataColumn.cls" module="cDataColumn" type="class" />
            <item5 gistid="3414216" version="" filename="cDataRow.cls" module="cDataRow" type="class" />
            <item6 gistid="3414216" version="" filename="cHeadingRow.cls" module="cHeadingRow" type="class" />
            <item7 gistid="3414346" version="" filename="" module="usefulStuff" type="module" />

idan

Hello there! This is a sample post for gist.io, a super-lightweight writing soapbox for hackers.

Now look up. Further. Above the post title. See that grey text with the gist ID?

Now back to me. That grey text is a link! Open that sucker in a new tab to see the source for this post. Also, I'm on a horse.

This is a major heading

If you peek at it with a web inspector, you'll see that it is a second-level heading. You can use first level headings, but they'll look just like the second level ones, and the gods of the HTML5 outlining algorithm will frown upon you.

brucemcpherson

'IMPORTANT - CHANGE gtExampleLoad() to include gtDoit() for each Gist you want to load
' bootstrap code to update VBA modules from gists
' all code is in this module - so no classes etc.
' latebinding is used to avoid need for any references
' can be found at https://gist.github.com/3403537
Option Explicit
' v2.04 - 3403537
' if you are using your own gists - change this
Const gistOwner = "brucemcpherson"

krisselden

trace-deopt.sh

How to use

./trace-deopt.sh http://localhost:4200

Wait until your page renders.

scottjehl

I wanted to figure out the fastest way to load non-critical CSS so that the impact on initial page drawing is minimal.

TL;DR: Here's the solution I ended up with: https://github.com/filamentgroup/loadCSS/

---

For async JavaScript file requests, we have the async attribute to make this easy, but CSS file requests have no similar standard mechanism (at least, none that will still apply the CSS after loading - here are some async CSS loading conditions that do apply when CSS is inapplicable to media: https://gist.github.com/igrigorik/2935269#file-notes-md ).

Seems there are a couple ways to load and apply a CSS file in a non-blocking manner:

shivangp

// ==UserScript==
// @name           Auto Check-In to Southwest Flights
// @namespace      https://gist.github.com/ryanizzo/058829a5fafe733bd876410db7a1e699
// @version        1.9
// @author         Nicholas Buroojy (http://userscripts.org/users/83813)
// @contributor    Ryan Izzo (http://www.ryanizzo.com)
// @contributor    JR Hehnly (http://www.okstorms.com @stormchasing)
// @contributor    Trevor McClellan (github.com/trevormcclellan)
// @description    Automatically check in to Southwest Airline flights at the appropriate time.
// @include        https://www.southwest.com/air/check-in/index.html*

jed

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

isaacs

# Hello, and welcome to makefile basics.
#
# You will learn why `make` is so great, and why, despite its "weird" syntax,
# it is actually a highly expressive, efficient, and powerful way to build
# programs.
#
# Once you're done here, go to
# http://www.gnu.org/software/make/manual/make.html
# to learn SOOOO much more.

bmhatfield

# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

# Add the following to your shell init to set up gpg-agent automatically for every shell
if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
    source ~/.gnupg/.gpg-agent-info
    export GPG_AGENT_INFO
else