Andrea Amantini

The error depends also on which values are being wrapped: 

I believe the reason for this is how `viewer/present` treats wrapped values: ```clojure [(viewer/present {:nextjournal/value (clerk/with-viewer viewer/string-viewer "hello")}) (viewer/present {:nextjournal/value (clerk/with-viewer viewer/number-viewer 123)})] ;; => [{:path [], ;; :nextjournal/value "hello",...

The same happens in a plain analyzer call, when the type is not yet in context: ```clojure (clojure.tools.analyzer.jvm/analyze '(reify Foo (-foo [this] :baz))) ;; throws ;; Execution error (NullPointerException) at...

I'd be also pretty interested in footnotes, trying to see what is missing from the current extensibility. I guess parsing the footnote body as custom blocks starting with `[^label]:` wouldn't...

@robinst thanks for looking into this! > why it's not done the same way as link reference definitions, where references are resolved during inline parsing I'd also expect a procedure...

I could gem install 'rb-gsl' under ruby 2.1.1. rb-gsl is maintained by SciRuby https://github.com/SciRuby/rb-gsl

Hi Mark, great, thank you for the feedback. no problem, if I get to that point I'll sure push a PR! > elixir binding > 👍 ciao for now... A.

> we wouldn't abandon effi for Cuneiform (if that was the suggestion). no, I didn't suggest that :-)! cuneiform _as a language_ definitely needs effi because of the command line....

also we're using `erlport` because we need a more fein-grained results-set (like per-line evaluations of the task) but nothing against the effi approach...

> Just encountered the same issue yes, still a problem, see https://github.com/nextjournal/markdown/pull/24.