calva 2026-11-01

Dear Calva friends: calva https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.607 • https://github.com/BetterThanTomorrow/calva/issues/3320 • Highlight grammar now styles keywords matching clojure-lsp’s semantic tokens • https://github.com/BetterThanTomorrow/calva/issues/3321 • https://github.com/BetterThanTomorrow/calva/issues/3322 • https://github.com/BetterThanTomorrow/calva/issues/3323 • https://github.com/BetterThanTomorrow/calva/issues/2869 • https://github.com/BetterThanTomorrow/calva/issues/2841 • https://github.com/BetterThanTomorrow/calva/issues/2838 • https://github.com/BetterThanTomorrow/calva/issues/2892 Thanks @conao3 for ParEdit Squeeze! 🙏 ❤️ The output view updates further makes the output view blend in and be more fully a Calva Clojure code view, plus making it more useful with scroll lock and ParEdit navigation and selection. There are also a bunch of fixes for the experimental repl input widget. More on that -> 🧵

❤️ 3

REPL Input widget fixes: • The REPL Input is highlighted the way files are: the grammar, the theme’s font styles, and clojure-lsp’s semantic tokens. In cljs and cljc contexts, clojure-lsp reads the code as ClojureScript. • It uses the editor’s background and text colors. • It has Calva’s rainbow brackets and rainbow indent guides. • Code in completion docs is colored the way files are. • While an evaluation runs, the context line shows a spinner and a stop button. • Scrolling the REPL Input doesn’t leak over to scrolling the output. • The REPL Input’s sash is 4px wide across the border, like VS Code’s sashes. • The REPL Input follows the editor into its namespace. Evaluating an ns or in-ns form for the followed file’s namespace also goes back to following the editor. • The lock choice is shared by both views. Choosing a mode in one view ends the other view’s hold from a history entry. It’s coming together pretty nicely, I’d say. I’m running with it enabled and the input convenience is great. No need at all for the REPL Window. Unless I run into some major issue the following few days, I’ll take the input widget out of experimental and write proper docs for it.

I've been using a bit and the presentation is very nice. I know there are two options, but I only see it in the sidebar. It's unclear to me whether it can be shown elsewhere?

🙏 1

Thanks for trying it out! The two options are available from the calva.outputDestinations setting, sidebar (`output-sidebar`) or editor area (`output-view`). The sidebar view can be moved to other panel positions, like beside your terminals or whatever you fancy.

Things I like: • It's pretty • Very clear what I'm doing • I like the compartimentalization, opening terminals is clunky and usually force me to use my mouse • Respect of the theme is very very nice Things I don't like so much: • if I close the output window, it clears it (well, it's actually strange. If I close it manually and re-open it with the keybind, it's empty. If I close it and re-open it by running a command, it has the history). • That's actually the only problem I have with it so far.

🙏 1

It’s not trivial what to do about the clearing. Part of what makes us keep the performance of the view is that we just append to its DOM and then forget about it. What I do with the editor-hosted view is that instead of closing it, I move it into my main editor group, usually the first View: Move Editor into First Group. Also, the sidebar view will keep the prints. Dunno if you are aware, but you can configure the output to go to both places. My settings are like so:

"calva.outputDestinations": {
    "evalResults": [
      "output-sidebar",
      "output-view",
      "terminal",
    ],
    "evalOutput": [
      "output-sidebar",
      "output-view",
      "terminal",
    ],
    "otherOutput": [
      "output-sidebar",
      "output-view",
      "terminal",
    ]
  },
Albeit, I will probably stop printing to the terminal soon, because the output views have caught up lately, and also surpassed. Btw: Calva has commands for revealing its output destinations. E.g: > opening terminals is clunky and usually force me to use my mouse Calva: Show/Open the Calva Output Terminal

All that said, @malaingreclement. Please file an issue about that unwanted clear.

Wow! Big changes. Nice!

🤘 1