idlecool

$ sudo yum update
$ sudo yum install openssl-devel
$ sudo yum install gcc-c++
$ wget -c http://znc.in/releases/znc-latest.tar.gz
$ tar -xzvf znc-latest.tar.gz
$ cd znc*
$ ./configure
$ make
$ sudo make install

takikawa

#lang racket

;; added something like `where` clauses

(require (for-syntax syntax/parse
                     syntax/parse/experimental/template))

(provide define/match)

(begin-for-syntax

areina

Manage your gmail account in emacs with mu4e

There're a lot of combinations to manage your email with emacs, but this works for me. I've a backup and I can manage my daily email.

The stack:

• emacs
• offlineimap
• mu
• mu4e

greghendershott

Before Github deploys the Racket lexer from pygments-main via pygments.rb, the following will appear as plain, black monospace. After they deploy, this will appear color-coded:

(let ([x 0])
  x)

Then it will look similar to the Scheme lexer (below) but, as the most glaring example, brackets will not be colored as errors:

greghendershott

A guide for new and/or casual contributors to Racket

Maybe you're comfortable with Git, but haven't made a pull request before.

Maybe you've made one-off pull requests, but haven't tried to contribute to the same project over time and stay in sync with the upstream project.

This guide may help. DRAFT

tonyg

Demonstrates the use of Racket's custodians and namespaces to create enough isolation to "reboot" programs without restarting the whole of Racket, including possibly recompiling and reloading code.

To experiment with this:

$ racket ~/src/racket-experiments$ racket
Welcome to Racket v5.3.1.4.
-> (require "reloader.rkt")
-> (load-and-foo)
Starting worker...

test-mod: "foo"

dyoo

#lang racket

(define (f x)
  (* x x))
(provide f)


(module* foo racket/base
  ;; External test of the function
  (require rackunit

dyoo

#lang racket

;; Experiment: interaction between compiled code and a tool.
;;
;; Typically, 3d syntax is often used here.  But let's say we don't
;; want 3d syntax.  Is there another way?
;;
;; Idea: when evaluating code, attach a module to the evaluating
;; namespace that the code and the tool share.
;;

soegaard

#lang racket
(require racket/draw (for-syntax syntax/parse) pict unstable/gui/pict)

(define-syntax defv (make-rename-transformer #'define-values))
(define-syntax defm (make-rename-transformer #'match-define))
(define-syntax def  (make-rename-transformer #'define))

(define-match-expander color:
  (λ (stx) 
    (syntax-parse stx 

khernyo

#!/bin/bash

set -e

SCRIPT_DIR=$( cd "$( dirname "$0" )" && pwd )

# the location of a clean racket repo which will be copied to avoid "git clone"-ing
REPO=$SCRIPT_DIR/../tools/racket

PLATFORM=linux-x86_64