Re: [O] ob-clojure.el is not compatible with new CIDER API

2018-07-29 Thread Tim Cross
No, there is no public repo and I'm not sure I even kept what little I had done - it was just a hacked elisp file. I'll have a look through my elisp archive, but don't expect much. Over the weekend, I caught up on a bit of clojure and things have progressed in the last few months. I notice the

[O] org-ref, html-export, citation links

2018-07-29 Thread Johannes Brauer
Hi! I have an older Html-file exported from an org-mode file with org-ref citations. All citation links are internal links into the reference section, fine! But if I anew export the org-mode file, now, the generated citation links are external file links to (not existing) files. For example,

Re: [O] ob-clojure.el is not compatible with new CIDER API

2018-07-29 Thread stardiviner
Tim Cross writes: > I did begin to look at it. From memory, the inf-clojure integration didn't > look that hard, > but it did require some additional scaffolding to mae the comms work well. I > then got > distracted with a new job and haven't had time to go back to it. Currently, > I've not

[O] ob-lilypond and 'Symbol’s function definition is void: org-babel-get-header'

2018-07-29 Thread Henrik Frisk
Hi, I have been trying out ob-lilypond and it works really well, except for the arrange mode. Any attempt to run ly-tangle results in 'Symbol’s function definition is void: org-babel-get-header' and so does an attempt to export a file, such as the example file, in basic mode to html for instance.

Re: [O] Feature request: Maintaining multiple init files with one org file

2018-07-29 Thread Sven Bretfeld
Hi Armin That's an interesting approach. I didn't think about giving arguments to the :tangle operator. This is basically what I was looking for. Just a bit more to write to each relevant source block. I will give it a try. Sven Amin Bandali writes: > Hello, > > Indeed, a tag-based solution

Re: [O] Feature request: Maintaining multiple init files with one org file

2018-07-29 Thread Sven Bretfeld
Hi Thanks for the answer. Tim Cross writes: > As your emacs init file is really just a lisp program, it is relatively > easy to implement multiple environment support within the file itself, > which is what I do. At the start of my init file, I just have some elisp > which sets variables