sc250024

#!/bin/bash

OLDIFS=$IFS
export IFS=$'\n'

# Find all boxes which have updates
AVAILABLE_UPDATES=$(vagrant box outdated --global | grep outdated | tr -d "*'" | cut -d ' ' -f 2 2>/dev/null)

if [[ ${#AVAILABLE_UPDATES[@]} -ne 0 ]]; then

floam

# Seems supported in $TERM_PROGRAM_VERSION 370
> cat nsterm-256color
# A xterm-256color based TERMINFO that adds the escape sequences for italic.
xterm-256color|xterm with 256 colors and italic,
  sitm=\E[3m, ritm=\E[23m,
  use=xterm-256color,
> tic nsterm-256color
> ENV TERM=nsterm-256color tput sitm; echo italics

junegunn

" ----------------------------------------------------------------------------
" vimawesome.com
" ----------------------------------------------------------------------------
function! VimAwesomeComplete() abort
  let prefix = matchstr(strpart(getline('.'), 0, col('.') - 1), '[.a-zA-Z0-9_/-]*$')
  echohl WarningMsg
  echo 'Downloading plugin list from VimAwesome'
  echohl None
ruby << EOF
  require 'json'

max-mapper

JavaScript function hoisting by example

Below are many examples of function hoisting behavior in JavaScript. Ones marked as works successfuly print 'hi!' without errors.

To play around with these examples (recommended) clone them with git and execute them with e.g. node a.js

Notes on hoisting

(I may be using incorrect terms below, please forgive me)

edouard-lopez

# Based on https://github.com/sass/libsass/wiki/Building-with-autotools

# Install dependencies
apt-get install automake libtool 

# Fetch sources
git clone https://github.com/sass/libsass.git
git clone https://github.com/sass/sassc.git libsass/sassc

# Create configure script

ericdouglas

// 4 spaces to 2 spaces
%s;^\(\s\+\);\=repeat(' ', len(submatch(0))/2);g

// Tab to 2 spaces
:%s/\t/  /g

ddeville

tell application "Safari"
	set current_tab to current tab of front window
	
	set tab_title to name of current_tab
	set tab_address to URL of current_tab
	
	tell application "Spillo"
		show create bookmark panel with properties {url:tab_address, title:tab_title}
	end tell
end tell

traviskaufman

Better Jasmine Tests With this

On the Refinery29 Mobile Web Team, codenamed "Bicycle", all of our unit tests are written using Jasmine, an awesome BDD library written by Pivotal Labs. We recently switched how we set up data for tests from declaring and assigning to closures, to assigning properties to each test case's this object, and we've seen some awesome benefits from doing such.

The old way

Up until recently, a typical unit test for us looked something like this:

describe('views.Card', function() {

javiermarinros

    // Simple script that exports a users "Saved For Later" list out of Feedly
    // as a JSON string.
    //
    // This was intended for use in the Google Chrome's "Inspector" tool so your
    // mileage may vary if used in other contexts.
    //
    // Format of JSON is as follows:
    //  [
    //    {
    //      title: "Title",

hihellobolke

#!/bin/bash
# [email protected]

SSHCONFIG_Linux=$(cat << 'HERE-DOC'

Host *
  StrictHostKeyChecking no
  ServerAliveInterval 60
  ForwardAgent yes
  ServerAliveCountMax 4