Skip to content

Auto REPL connect and minor quality of life improvements

Compare
Choose a tag to compare
@Olical Olical released this 08 Sep 17:22
· 951 commits to master since this release
566915c

Hello! I survived presenting at vimconf (Conversational Software Development: What, Why and How?) and can finally release some small improvements I've been sitting on for too long + some more things from yesterday.

I like to use the develop branch in anger at work for a day or two to make sure there's no obvious issues before I release which slows things down a little. Here's the changes!

  • The log wrapping option got a lot safer, you can pass falsy things to it now and it won't explode.
  • Don't load Conjure clients if you launch nvim in diff mode, this avoids the overhead of booting up and attempting connections when you're trying to fly through git conflict resolutions.
  • Link to the FAQ when Conjure's nREPL Clojure support encounters a weird environment that can't be identified as Clojure, ClojureScript or ClojureCLR.
  • Auto connect on eval and other actions when you don't have a connection for Janet and Clojure! This means you can just jump into a file, start your REPL then start evaluating code. Conjure will make a connection if it can / needs to.
  • Update the sponsors list (omg it keeps growing, you're all wonderful, thank you so much ❤️)
  • Improve port-file resolution for Clojure, it now checks the parents of the current file, then the current working directory and finally ~/.config/conjure. This means you can :cd to a directory containing a .nrepl-port file then open a file from a local library you're working on that's in another tree. Conjure will now successfully connect to the nREPL from your CWD!
  • Resolve the log buffer path fully before attempting to open a window, this ensures you don't see weird errors when performing evaluations, changing working directory and then running more. Before it would get into a weird state where it created a new log buffer under the new CWD. It'll reuse the original log buffer correctly now.
  • Make Clojure completion context optional (see the bottom of the Clojure help). I found this to be a source of heavy CPU slowdown on slower machines, so you can turn this off if you need to. I hope this will get massively faster (suddenly instant with low CPU) on the advent of tree-sitter.

And that's all for today! I hope you enjoy the changes and it works well for you! I hope the next update will be out quickly with a few more fixes 😄 enjoy!

Have a great rest of your week!

image