Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

https://github.com/nextjournal/clerk

⚡️ Moldable Live Programming for Clojure
https://github.com/nextjournal/clerk

clojure live-programming moldable-development notebook repl visualization

Last synced: 16 days ago
JSON representation

⚡️ Moldable Live Programming for Clojure

Lists

README 

        
![Clerk: Local-First Notebooks for Clojure](https://cdn.nextjournal.com/data/QmQfj66AwEThMukaNiAcvKuBxTo1oF8XYmUH8ewbG8aXqy?filename=Clerk-GitHub.png&content-type=image/png)



# Clerk



[![Clojars Project](https://img.shields.io/clojars/v/io.github.nextjournal/clerk.svg)](https://clojars.org/io.github.nextjournal/clerk)



## Moldable Live Programming for Clojure



[🎪 View Demos](https://github.clerk.garden/nextjournal/clerk-demo/) •

[📖 Book of Clerk](https://book.clerk.vision)

[👩‍🎨 Using Clerk](#-using-clerk) •

[🪚 Development](#-developing-clerk)



Clerk takes a Clojure namespace and turns it into a notebook:



![Clerk Screenshot](https://cdn.nextjournal.com/data/QmeJvCtv5xqD8T7y2L3fwjnvWyCZM4DDk2iuspjqaC9QFc?filename=Screenshot+2022-09-18+at+20.09.14.png&content-type=image/png)



## 🎪 [Demos](https://github.clerk.garden/nextjournal/clerk-demo/)



Clerk comes with a [demo repo](https://github.com/nextjournal/clerk-demo/) full of interesting use cases. Check them out and feel free to add your own via PRs.



## ⚖️ Rationale



Computational notebooks allow arguing from evidence by mixing prose with executable code. For a good overview of problems users encounter in traditional notebooks like Jupyter, see [I don't like notebooks](https://www.youtube.com/watch?v=7jiPeIFXb6U) and [What’s Wrong with Computational Notebooks? Pain Points, Needs, and Design Opportunities](https://www.microsoft.com/en-us/research/uploads/prod/2020/03/chi20c-sub8173-cam-i16.pdf).



Specifically Clerk wants to address the following problems:



* Less helpful than my editor

* Notebook code being hard to reuse

* Reproduction problems coming from out-of-order execution

* Problems with archival and putting notebooks in source control



Clerk is a notebook library for Clojure that aims to address these problems by doing less, namely:



* no editing environment, folks can keep using the editors they know and love

* no new format: Clerk notebooks are either regular Clojure namespaces (interspersed with markdown comments) or regular markdown files (interspersed with Clojure code fences). This also means Clerk notebooks are meant to be stored in source control.

* no out-of-order execution: Clerk notebooks always evaluate from top to bottom. Clerk builds a dependency graph of Clojure vars and only recomputes the needed changes to keep the feedback loop fast.

* no external process: Clerk runs inside your Clojure process, giving Clerk access to all code on the classpath.



## 🚦 Status

ALPHA, expect breaking changes.



## 👩‍🎨 Using Clerk



To use Clerk in your project, you'll need Java 11+ and [`clojure`](https://clojure.org/guides/install_clojure). Add the

following dependency to your `deps.edn`:



```edn

{:deps {io.github.nextjournal/clerk {:mvn/version "0.16.1016"}}}

```



Require and start Clerk as part of your system start, e.g. in `user.clj`:



```clojure {:nextjournal.clerk/code-listing true}

(require '[nextjournal.clerk :as clerk])



;; start Clerk's built-in webserver on the default port 7777, opening the browser when done

(clerk/serve! {:browse true})



;; either call `clerk/show!` explicitly

(clerk/show! "notebooks/rule_30.clj")



;; or let Clerk watch the given `:paths` for changes

(clerk/serve! {:watch-paths ["notebooks" "src"]})



;; start with watcher and show filter function to enable notebook pinning

(clerk/serve! {:watch-paths ["notebooks" "src"] :show-filter-fn #(clojure.string/starts-with? % "notebooks")})



;; Build a html file from the given notebook notebooks.

;; See the docstring for more options.

(clerk/build! {:paths ["notebooks/rule_30.clj"]})

```



You can then access Clerk at .



See the [/notebooks folder](https://github.com/nextjournal/clerk/tree/main/notebooks) in the Clerk repository for a number of sample notebooks.



### Editor Workflow



For even better flow states, we recommend you bind `clerk/show!` to a shortcut in your favorite editor:



#### Emacs



In Emacs, add the following to your config:



```elisp

(defun clerk-show ()

  (interactive)

  (when-let

      ((filename

        (buffer-file-name)))

    (save-buffer)

    (cider-interactive-eval

     (concat "(nextjournal.clerk/show! \"" filename "\")"))))



(define-key clojure-mode-map (kbd "") 'clerk-show)

```



#### IntelliJ/Cursive



In IntelliJ/Cursive, you can [set up REPL commands](https://cursive-ide.com/userguide/repl.html#repl-commands) via:



* going to `Tools→REPL→Add New REPL Command`, then

* add the following command: `(show! "~file-path")`;

* make sure the command is executed in the `nextjournal.clerk` namespace;

* lastly assign a shortcut of your choice via `Settings→Keymap`



#### Neovim + Conjure



With [neovim](https://neovim.io/) + [conjure](https://github.com/Olical/conjure/) one can use the following vimscript function to save the file and show it with Clerk:



```vimscript

function! ClerkShow()

  exe "w"

  exe "ConjureEval (nextjournal.clerk/show! \"" . expand("%:p") . "\")"

endfunction



nmap  cs :execute ClerkShow()

```



## 🪚 Developing Clerk

Make sure you have [Babashka installed](https://github.com/babashka/babashka#installation), and run:



```bash

bb dev :browse true

```



The will start everything needed to develop Clerk and open your

default browser. You can connect your favorite editor to it using nREPL.



Any trailing arguments to `bb dev` will be forwarded to `clojure -X`

and `clerk/serve!`. So if you prefer to not open your browser, leave 

out the `:browse true` arguments.



## 🐞 Known Issues



See [notebooks/onwards.md](https://github.com/nextjournal/clerk/blob/main/notebooks/onwards.md).



## Citing Clerk



If you are a researcher and use Clerk in your work, we encourage you to cite our work.

You can use the following BibTeX citation:



```bibtex

@misc{clerk-github,

  author =  {Martin Kavalar and

             Jack Rusher},

  title = {{Clerk Source Code}},

  howpublished = {\url{https://github.com/nextjournal/clerk}},

  month        = feb,

  year         = 2023

}

```