Dear Calva Backseat Driver friends: https://github.com/BetterThanTomorrow/calva-backseat-driver/releases/tag/v0.0.10 • Use preconfigured port for the MCP server • Make the stdio wrapper script accept either a port or a port file It’s a bit trick yto support MCP because every AI agent vendor seems to have at least one different idea about how to support it, and what to support. But now I think the most common clients are covered as best as we can.
Dear Calva friends, Calva version 2.0.509 is released, and includes a new output view! This work has been supported by funding from Clojurists Together ❤️. The new output view is a work in progress, and it would be greatly appreciated if you try it out and report any bugs you see, feature enhancements you'd like, or behavior changes you'd like. Work will continue on this output view and new features will be added. This view is intended to address shortcomings of other output destinations and give us more flexibility for adding features. To try out this new output view, you can set any or all of your https://calva.io/output/#output-destinations to "output-view". You can copy and paste the settings below into your VS Code settings file and update it to what you'd like:
"calva.outputDestinations": {
"evalResults": "output-view",
"evalOutput": "output-view",
"otherOutput": "output-view"
}
Please refer to the documentation for more info:
• https://calva.io/output-view/
• https://calva.io/output/#output-destinations-feature-comparison
CC @pez (Thanks for your review and guidance on this.)I've really gotten used to the terminal output -- and I like that it clusters with the jack-in (terminal) window and my regular terminal (at the bottom). This new output view pops up in a different place and doesn't seem to have the syntax highlighting that the terminal has? Output was all uniformly brown whereas terminal highlights keywords, strings, brackets etc.
I think the syntax highlighting doesn’t always work in the new output view.
Ah, OK. Good to know that the "bad" behavior is "expected" (or at least "known")
I think at this point, I'll stick with terminal because I like the workflow/placement (I have a narrow slot of multiple terminals at the bottom of my screen, that I can cycle through with ctrl+pagedown, with ctrl+t ctrl+f to switch the focused terminal, and ctrl+1 to jump back to my code editor).
I’ve put some comments on the PR with things I’ve found. Some of which should probably be converted to issues: https://github.com/BetterThanTomorrow/calva/pull/2481
Regarding placement, we are tracking this here: https://github.com/BetterThanTomorrow/calva/issues/2813
It can’t ever be placed as a terminal, since it is not a terminal, but I think we can add more flexibility than we now have. Remains to be proven.
It’s very WIP. If you do try it out now and then. Please report issues.
Looking at the comparison page, terminal and output-view seem functionally "identical" right now -- and the future features for output-view are things I don't want/need 🙂 So the position/placement is the big issue for me and the main reason I switched to terminal in the first place. So, please don't remove terminal at any future date!
The terminal output destination is not going anywhere. No worries.
https://github.com/orgs/BetterThanTomorrow/projects/3 > I’ve put some comments on the PR with things I’ve found. Some of which should probably be converted to issues I've converted some to draft issues in the project board linked, which I just made public. I made them draft issues before I released the output view, but I'll be converting them to actual issues soon. There are a couple that I'd like you to create issues for that I noted in the PR, @pez. Pasting here for visibility:
I've not yet experienced missing syntax highlighting in the output view. I suspect maybe it's some issue with pulling the highlightjs resources from the internet.
Those might be added locally so internet isn't required
Are there screenshots of the new view anywhere?
It doesn't look much different than the terminal right now, except that it's a panel that can be moved anywhere like an editor panel, rather than a fixed terminal.
No there aren’t screenshots in the docs but we should add some and/or gifs.
It’s amazing the things you can overlook even when you’re trying to be thorough 😅
Or at least, I speak for myself there lol