janko

require "benchmark/ips"

File.write "minitest_test.rb", <<-EOS
require "minitest/autorun"
require "minitest/pride"

class MintestTest < Minitest::Test
  def test_foo
    assert true
  end

NZKoz

• Install getmail (aptitude install getmail4)
• Set Up Your Imap Server (tl;dr)
• getmail
• ruby date_based_archive.rb ~/Maildir/.Archive

threedaymonk

 ~ > cat /etc/fstab 
proc            /proc           proc    defaults        0       0
/dev/mmcblk0p1  /boot           vfat    defaults        0       0
/dev/mmcblk0p2  /               ext4    defaults,noatime,nodiratime     0    0
#/dev/mmcblk0p3  none            swap    sw              0       0

sugendran

#!/bin/sh
# A script to build your iOS app and send it to test flight
# Distributed on an as is and I accept no responsiblity for what it does licence
# For more info: http://www.abandonedexpression.com/2011/06/continuous-integration-with-xcode.html

# I'm assuming that your project is in the src directory of your repository
PROJECT_DIRECTORY="${PWD}/src"
# The target we're building
TARGET_NAME="My Project"
# The name for the .app and .ipa files that get created

xaviershay

Hello Github,

Pull requests are not serving me well on large reviews. Here are some problems and suggested enhancements that would make me happy.

• Mark comment as "resolved" (see google docs for an example). As code changes, comments get lost or made redundant, and it is not clear (to either the author or reviewers) which are still relevant and which have been addressed. Resolving a comment doesn't need to make it dissappear, but I need to be able to see "which comments have not been addressed" somehow. This feature would be the most useful to me.
• Reply to a comment. This can be done in effect on line comments (assuming there is only one), but cannot on PR comments. Particularly with many threads, the lack of this makes a review hard to follow.
• Explicit "approve/block" life cycle. The block is actually more important to me ... often on a PR that has been incrementally improved I want to "block" final merge of it until I get a chance to rebase/squash and generally pretty it up. The block can be over

evadne

defmodule StreamIterator.Messages do
  @moduledoc """
  The Stream Iterator can be used to consume items from an Elixir Stream incrementally.

  ## Examples
  
  ### Infinite Streams

  When used on infinite streams such as the ones returned by `Stream.cycle/1`, the Stream
  Iterator will always return the next item.

ajosanchez

class Hack
  
  def initialize words
    @words = words.downcase.split(/\/|\s|,\s|\,/)
    @splitwords = []
    @words.each { |w| @splitwords << w.split('') }
    show_likely
  end
  
  def deduct

myobie

Get Mountain Lion and Homebrew to Be Happy

1) Install XCode 4.4 into /Applications

Get it from the App Store.

2) Install Command Line Tools

In XCode's Preferences > Downloads you can install command line tools.

masonforest

Installing a Gem on Heroku from a Private GitHub Repo

Sometimes you want to use a gem on Heroku that is in a private repository on GitHub.

Using git over http you can authenticate to GitHub using basic authentication. However, we don't want to embed usernames and passwords in Gemfiles. Instead, we can use authentication tokens.

1. Get an OAuth Token from GitHub

---

First you will need to get an OAuth Token from GitHub using your own username and "note"

chrismccord

If you want a run-down of the 1.3 changes and the design decisions behidn those changes, check out the LonestarElixir Phoenix 1.3 keynote: https://www.youtube.com/watch?v=tMO28ar0lW8

To use the new phx.new project generator, you can install the archive with the following command:

$ mix archive.install https://github.com/phoenixframework/archives/raw/master/phx_new.ez

Bump your phoenix dep

Phoenix v1.3.0 is a backwards compatible release with v1.2.x. To upgrade your existing 1.2.x project, simply bump your phoenix dependency in mix.exs: