rksm

#!/bin/bash


# -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
# 1. Install packages
if [[ ! -d lively-loader ]]; then
  git clone -b master https://github.com/LivelyKernel/node-lively-loader lively-loader
  pushd lively-loader;
  npm install;
  popd

rksm

var exec = require("child_process").exec;
var path = require("path");
var fs = require('fs');
var util = require("util");

var enabled = false;

var sslDir = path.join(process.env.HOME, "lively-web.org/http/ssl/");
var outDir = path.join(sslDir, "lively-web-CA");
var registerCertScript = path.join(sslDir, "register-cert.sh");

rksm

wget https://github.com/cloxp/cloxp-install/releases/download/pre-0.0.8/cloxp-pre-0.0.8.zip
unzip cloxp-pre-0.0.8.zip
./install.sh
cd LivelyKernel
sed -i '' 's|+refs/tags/cloxp-pre-0.0.8:refs/tags/cloxp-pre-0.0.8|+refs/heads/*:refs/remotes/origin/*|' .git/config
git fetch origin clojure-support
git checkout clojure-support
npm update
cd ..;
./start.sh

rksm

;; quite useful:
;; http://www.aaronbedra.com/emacs.d/


;; basic settings
(setq inhibit-splash-screen t
      initial-scratch-message nil
      initial-major-mode 'org-mode)
 
(scroll-bar-mode -1)

rksm

and static typing shouldn't go together with an interactive workflow and live programming.
On the contrary, static analysis can help interactive tooling a lot. Refactorings,
code browsing, dependency analysis that are implemented in main stream dev envs certainly
show that. And then there is "Hole-driven development" [1], code synthesis,
constraint and satisfiability solvers like [2] that can make programming more
declarative and require a powerful underlying meta system. From this
perspective Unison is an exciting project indeed.

For some reason, however, it seems to me that the Haskell community (apart from
Elm) doesn't really seem to be too interested in that topic. There is Don

rksm

FROM          dockerfile/nodejs
MAINTAINER    Robert Krahn <[email protected]>

USER root
ENV DEBIAN_FRONTEND noninteractive
RUN apt-get update
RUN apt-get install -y \
    python-software-properties \
    curl wget git \
    less manpages manpages-dev \

rksm

(def ^:dynamic *test-subject* nil)

(defn subject-fixture [test]
  (binding [*test-subject* {:foo 23}]
    (test)))

(use-fixtures :each subject-fixture)

(deftest my-test
  (is (= *test-subject*

rksm

(function loadUserKeyBindings() {
  // user key bindings
  try {
    var cust = JSON.parse(lively.LocalStorage.get("user-key-bindings"));
    ace.ext.keys.addKeyCustomizationLayer("user-key-bindings", cust || {});
    var h = ace.require("ace/keyboard/keybinding").KeyBinding.prototype["ace.ext.keys.customized"].detect(function(ea) {
      return ea.layerName === "user-key-bindings"; })

    var proto = ace.ext.keys.KeyHandlerForCustomizations.prototype
    proto.handleKeyboard = proto.handleKeyboard.getOriginal().wrap(function (proceed, data, hashId, keyString, keyCode) {

rksm

module('users.YOUR-USERNAME.config').requires().toRun(function() {

lively.Config.set("useEmacsyKeys", false);

module("lively.ide.CodeEditor").runWhenLoaded(function() {

  ace.config.loadModule(["keybinding", 'ace/keyboard/vim'], function(vim) {
    lively.Config.codeEditorUserKeySetup = function(editor) {
      editor.withAceDo(function(ed) {
        ed.keyBinding.addKeyboardHandler(vim.handler);

rksm

lively.morphic.CodeEditor.prototype.setTheme = lively.morphic.CodeEditor.prototype.setTheme
  .getOriginal().wrap(function(proceed) { return proceed("monokai"); });

// -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

lively.whenLoaded(function() {
  (function() {
  $world.get("MenuBar").addStyleClassName("MenuBar");
  $world.withAllSubmorphsDo(function(ea) { return ea.applyStyle({cssStylingMode: true, cssStyling: true}); });