conjure

Conversational software development for Neovim Conjure is an interactive environment for evaluating code within your running program. The core features of Conjure are language agnostic (although it’s targeted at Lisps for now), with each language client providing their own extra tools. Here’s the currently supported languages, contributions and 3rd party plugins that add clients are highly encouraged! You can find a comparison table for all clients and supported features in the wiki. Clojure over nREPL (quickstart) Babashka (quickstart) Basilisp (quickstart) Fennel inside Neovim via Lua and nfnl (quickstart) Fennel outside of Neovim within any Lua process through an stdio REPL (quickstart) Janet over spork/netrepl (quickstart) Janet over stdio (quickstart) Racket over stdio (quickstart) Hy over stdio (quickstart) Scheme (MIT by default) over stdio (quickstart) Guile over a socket file (quickstart) Common Lisp over Swank (quickstart) Julia over stdio (quickstart) Rust over stdio with evcxr (quickstart) Lua inside Neovim (quickstart) Python over stdio (quickstart) PHP over stdio with psysh (usage) R over stdio. JavaScript (using Node.js) over stdio Snd / s7 (sound editor scriptable with Scheme) over stdio SQL (PostgreSQL psql by default) over stdio Ruby (using irb) over stdio Elixir over stdio You can learn more about the mappings and configuration inside Neovim with :help conjure. Each language client also has it’s own specific help text under :help conjure-client-{LANGUAGE}-{TRANSPORT}, such as :help conjure-client-clojure-nrepl, which contains specific mappings and configuration for that client. You can also get an interactive guide to the core principals and mappings by executing :ConjureSchool or by using the "try before you install" script as described further down this page. User experience What does wielding Conjure actually look like? What can you do with it? YouTube: How I use Conjure and Neovim to interact with Clojure (and more!) Asciinema (see below) Open a file of a supported file type such as clojure or racket. Some languages, such as Clojure, will automatically connect to your REPL or give you the commands and mappings to do so yourself. Use various mappings to execute the code you’re interested in such as the current form, file, buffer or even form at a Neovim mark. Every result is kept in a log buffer that you can access at any time. Support for multiple asynchronous autocompletion frameworks, with deoplete built in (<C-x><C-o> also works!). You can also use nvim-cmp with cmp-conjure. (which I actually recommend!) Conjure allows you to send the right part of your code off for evaluation, see the results, wrap the results in more code and evaluate that. It keeps a log of your actions and results so you don’t have to remember them, that context is extremely helpful when you’re down the rabbit hole of a bug hunt. Evaluating a form under your cursor is as simple as <prefix>ee, where <prefix> defaults to <localleader>. Be sure to set your your <localleader> key or configure Conjure to use a different mapping prefix, see :h maplocalleader and :h g:conjure#mapping#prefix for more information. The goal is to give you a tool that lets you effortlessly run whatever you need to while keeping out of your way (but there with context and more information if you need it). Once installed you can run :ConjureSchool to begin an interactive tutorial. Try without installing You can trial run Conjure with the interactive :ConjureSchool tutorial without actually installing it! The only prerequisites are curl and an up to date nvim. curl -fL conjure.oli.me.uk/school | sh This will temporarily download the plugin, launch Neovim with :ConjureSchool running and then clean up after itself. You get to try out what Conjure has to offer without having to edit your Neovim configuration. Installation Requires Neovim 0.10 or newer. Alternatively you can use Magic Kit, an opinionated starter kit that includes all sorts of essential tools. packer.nvim use 'Olical/conjure' vim-plug Plug 'Olical/conjure' lazy.nvim return { "Olical/conjure" } To take advantage of lazy loading, a bit more involved configuration is required: Details return { { "Olical/conjure", ft = { "clojure", "fennel", "python" }, -- etc lazy = true, init = function() -- Set configuration options here -- Uncomment this to get verbose logging to help diagnose internal Conjure issues -- This is VERY helpful when reporting an issue with the project -- vim.g["conjure#debug"] = true end, -- Optional cmp-conjure integration dependencies = { "PaterJason/cmp-conjure" }, }, { "PaterJason/cmp-conjure", lazy = true, config = function() local cmp = require("cmp") local config = cmp.get_config() table.insert(config.sources, { name = "conjure" }) return cmp.setup(config) end, }, } Configuration All configuration is performed through global Neovim variables, this may change to a .setup(…​) Lua first approach some day but for now you can configure things by setting variables early, before Conjure loads. For example, if you wish to rebind or disable the default documentation lookup key (K) because you don’t need it or it conflicts with your LSP configuration you can do so like this: -- Disable the documentation mapping vim.g["conjure#mapping#doc_word"] = false -- Rebind it from K to <prefix>gk vim.g["conjure#mapping#doc_word"] = "gk" -- Reset it to the default unprefixed K (note the special table wrapped syntax) vim.g["conjure#mapping#doc_word"] = {"K"} # And the same disabling but in Vim Script # Note the v:false in Vim Script! let g:conjure#mapping#doc_word = v:false Please see :help conjure for the full list of possible configuration variables and values. Mods Modifications or