lispmeister

* Development process

** Feature Tracking

The first step of development should be to have a task card. Typically
the team leads will create the cards, but this won't always be true---sometimes
you'll find a bug or take a bug from a Flowdock conversation. At that point you
can ask your team lead to handle the card, or you can do it yourself. If you
create a card that you're intending on working on immediately, make sure to put

lispmeister

export RUST_BACKTRACE=1 ; target/debug/sit web                  
SIT needs your authorship identity to be configured

What is your name? fix
What is your e-mail address? fix@deeprecursion.com
thread 'main' panicked at 'can't open config file for writing: Os { code: 2, kind: NotFound, message: "No such file or directory" }', libcore/result.rs:1009:5
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
             at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::print

lispmeister

use "process"
use "files"
use "options"

actor Main
  let _env: Env

  new create(env: Env) =>
    _env = env
    var lines: (I64 | None) = None

lispmeister

ldd helloworld

	linux-vdso.so.1 (0x7ee06000)
	libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0x76f07000)
	libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0x76ef4000)
	libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0x76e79000)
	libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0x76e4c000)
	libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0x76d0b000)
	/lib/ld-linux-armhf.so.3 (0x54b3c000)

lispmeister

Keybase proof

I hereby claim:

• I am lispmeister on github.
• I am lispmeister (https://keybase.io/lispmeister) on keybase.
• I have a public key whose fingerprint is BE4E C1F4 9A9C A511 23A0 B1C5 0EE6 5961 52C4 3D41

To claim this, I am signing this object: