James Craig Burley

> I'm gonna try https://github.com/peterh/liner. [Joker](https://github.com/candid82/joker) has since migrated to its author's own [fork](https://github.com/candid82/liner) of `liner`. Seems to be working quite well so far!

> I switched to peterh/liner myself. Why the fork of it? Not sure exactly -- I think @candid82 explained it somewhere (maybe Slack), something to do with adding a feature,...

> So it's a fork before a future pull request Unsure, though I don't see any pertinent open PRs. He might have found a pertinent closed PR that was deemed...

@tom-seddon -- what's going on with your patch? Seems like some kind of fix is needed, but (while I'm comfortable with Go now) I don't know readline stuff well enough...

Is this perhaps responsible for: https://github.com/candid82/joker/issues/103 ?

> E.g., in my Emacs config for clj-refactor, I've enjoyed the consistency and auto-requiring of this: > > ```emacs-lisp > ("walk" . "clojure.walk") > ... > ("w" . "clojure.walk") >...

This appears to be due to relying on `fmt.Printf()`, which evidently does not support `%u` (`%d` would suffice, so I've changed my code to use that). See: https://golang.org/pkg/fmt/

Note that I've Deferred that work for now, but if anyone wants to try to track down what could actually be a bug in the C code that is (so...

Iteratively hand-converting the generated code has hidden or fixed the issue, as of this commit: https://github.com/jcburley/LispZeroGo/commit/0f1fe73aa75dece7352d856e8b4ef7d83cd61c4a I think it's likely the problem was due to unsafe pointers being hidden from...

The crashes have returned (but only when profiling): https://github.com/jcburley/lisp-zero-go/issues/1#issuecomment-419319253