This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (21)
- # announcements (1)
- # beginners (36)
- # boot (48)
- # cider (21)
- # clojure (61)
- # clojure-italy (4)
- # clojure-japan (5)
- # clojure-norway (2)
- # clojure-russia (2)
- # clojure-sg (2)
- # clojure-uk (3)
- # clojurescript (33)
- # core-async (5)
- # core-typed (1)
- # cursive (13)
- # datomic (34)
- # devops (38)
- # editors (24)
- # events (10)
- # ldnclj (14)
- # off-topic (31)
- # onyx (4)
- # re-frame (84)
and when a file was the result of cross-compilation the cljx file was used instead of the compiled one
i don't work on that project anymore but acc my memories this worked fine with cljx files
Anybody using org-babel to produce documents that mix definitions and REPL interactions?
I.e. My definitions are in blocks starting
#+BEGIN_SRC clojure :results silent
and the REPL interactions in
#+BEGIN_SRC clojure :results pp code :exports both :wrap "SRC clojure :eval no"
but the exported HTML doesn't distinguish them, so I can't style them differently.
I'm sure there's a way to make them distinguishable from html (though you clearly know more about org-export then I do)
@robert-stuttaford: I see the
bad state errors on any namespace that requires
clj-uuid - in that case it’s actually a Clojure problem to do with non-qualified return type hints - http://dev.clojure.org/jira/browse/CLJ-1232
@stuartsierra: I haven't tried styling my org-babel output, but it looks like you can do that with #+HTML_HEAD . Also more advance techniques described at http://emacs.stackexchange.com/questions/3374/set-the-background-of-org-exported-code-blocks-according-to-theme
fhanreich: there’s no official archive, but I know someone is archiving this particular slack. Can’t seem to find the link at the moment, though...
@jcsims: Thank you. Maybe I should ask @robert-stuttaford. I vaguely remember him mentioning about the bots...