With Ruby 1.8 (default version on MacOS) :
sudo gem install json
curl -s https://api.github.com/orgs/[ORGANIZATION]/repos | ruby -rubygems -e 'require “json”; JSON.load(STDIN.read).each {|repo| %x[git clone #{repo["ssh_url"]} ]}'
With Ruby 1.9+, the json library is by default thus you just use :
| ;;;; In response to: | |
| ;;;; | |
| ;;;; http://www.reddit.com/r/lisp/comments/3710zq/directed_procrastination_backtracking_with_the/ | |
| ;;;; http://directed-procrastination.blogspot.se/2011/05/backtracking-with-common-lisp-condition.html | |
| ;;;; | |
| ;;;; Demonstrating why one should not use conditions for this kind of stuff, | |
| ;;;; instead using the dynamic binding and unwinding facilities on which the | |
| ;;;; condition system is built. The author's backtracking system doesn't compare | |
| ;;;; badly to Screamer because his is simple: it compares badly because using | |
| ;;;; conditions is a bad match for the task. |
| -module(curry). | |
| -export([curry/1]). | |
| curry(F) -> | |
| {arity, Arity} = erlang:fun_info(F, arity), | |
| curry(F, [], Arity). | |
| curry(F, Args, 0) -> | |
| apply(F, lists:reverse(Args)); |
| ; Short guide to UDP/IP Client/Server programming in Common Lisp using usockets | |
| ; | |
| ; The main reason for this guide is because there are very few examples that | |
| ; explain how to get started with socket programming with Common Lisp that I | |
| ; could understand. | |
| ; After working on a short example on TCP, I found the | |
| ; need for a UDP tutorial. So, here goes. | |
| ; As usual, we will use quicklisp to load usocket. |
| ; Short guide to TCP/IP Client/Server programming in Common Lisp using usockets | |
| ; | |
| ; The main reason for this guide is because there are very few examples that | |
| ; explain how to get started with socket programming with Common Lisp that I | |
| ; could understand. After spending a day trying, I finally came up with a small | |
| ; bit of code that makes it easy to understand the basics. I've written this | |
| ; primarily for myself, but should help others get started as well. | |
| ; As usual, we will use quicklisp to load usocket. |
| // Just before switching jobs: | |
| // Add one of these. | |
| // Preferably into the same commit where you do a large merge. | |
| // | |
| // This started as a tweet with a joke of "C++ pro-tip: #define private public", | |
| // and then it quickly escalated into more and more evil suggestions. | |
| // I've tried to capture interesting suggestions here. | |
| // | |
| // Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_, | |
| // @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant, |
