loganlinn

(ns history
  "Light wrappers and utils for js/history")

(defn back! [] (.back js/history))

(defn forward! [] (.forward js/history))

(defn go! [idx] (.go js/history idx))

(defn replace-state!

allgress

(ns reagent-test.core
  (:require [reagent.core :as reagent :refer [atom]]
            [datascript :as d]
            [cljs-uuid-utils :as uuid]))

(enable-console-print!)

(defn bind
  ([conn q]
   (bind conn q (atom nil)))

ftrain

;; This is at: https://gist.github.com/8655399

;; So we want a rhyming dictionary in Clojure. Jack Rusher put up
;; this code here:
;; 
;; https://gist.github.com/jackrusher/8640437
;;
;; I'm going to study this code and learn as I go.
;;
;; First I put it in a namespace.

marshallbrekka

(defn keys->strings
  "Given a map converts all keys that are keywords from dash-separated to
   camel-case using key->string."
  [m]
  (let [f (fn [[k v]] [(key->string k) v])
        walk-fn (fn [x]
                  (if (map? x)
                    (->> (map f x)
                         (into {}))
                    x))]

jackrusher

Object-orientation

There are many articles and discussion threads on the web regarding the nature of Object-oriented (OO) programming. Most of them come at the question from a Programming Language Theory (PLT) perspective, attempting to assert a formal definition of OO programming and objects. I'm not going to do that here. Instead, I'm going to write about objects from an implementation perspective, approaching the subject first from below and then from above.

jasonrudolph

5 entertaining things you can find with the GitHub Search API

Let's have some command-line fun with curl, [jq][1], and the [new GitHub Search API][2].

Today we're looking for:

• The hottest repositories created in the last week.
• The oldest user accounts with zero followers. (So sad.)
• Issue trends by language.
• Clojure projects defying convention.

zpao

/** @jsx React.DOM */
var MyComponent = React.createClass({
  render: function() {
    // Defaults in case the props are undefined. We'll have a solution for this
    // soon that is less awkward.
    var perMinute = this.props.perMinute || '-';
    var perDay = this.props.perDay || '-';
    return (
      <div>
        <h3>Clickouts</h3>

nblumoe

fireplace

• cpr => (require ... :reload)
• cpR => (require ... :reload-all)

Evaluation

• :Eval (clojure code) => runs (clojure code) in repl
• cpp => evaluate inn-most expessions under cursor
• cp<movement> => evaluate text described by <movement>
• cqp => opens quasi-repl
• cqc => quasi-repl command line window

alandipert

ClojureScript macros: kinda, sorta, not really.

ClojureScript does not have a standalone macro system. To write ClojureScript macros, one must write them in Clojure and then refer to them in ClojureScript code. This situation is workable, but at a minimum it forces one to keep ClojureScript code and the macros it invokes in separate files. I miss the locality of regular Clojure macros, so I wrote something called maptemplate that gives me back some of what I miss. The technique may be useful in other scenarios.

Problem

Suppose you're wrapping functionality in another namespace or package so that you can have your own namespace of identically named but otherwise decorated functions:

ClojureScript:

andreyvit

tmux cheat sheet

(C-x means ctrl+x, M-x means alt+x)

Prefix key

The default prefix is C-b. If you (or your muscle memory) prefer C-a, you need to add this to ~/.tmux.conf:

remap prefix to Control + a