Clojurians Log v2
calva
Dear Calva friends: calva https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.576 • https://github.com/BetterThanTomorrow/calva/issues/3182 Now you can bind a keystroke to load a specific file in the REPL. Or write #joyride code that dynamically loads whatever file. See https://calva.io/commands/#repl-commands for the details.
Hello hello! I wanted to try out the joyride sidecar example and stumbled over vscodes handling of extensions with profiles. One needs to specify the profile where the extension should be installed to. Because it took me some time to find out I created an issue/pr to just add a comment to the example how to do it.
Thanks! Merged!
Well, thank you for joyride and the sidecar 🙂
Joyride is seriously underused in general, I think. Makes me happy when I learn about it being put to use.
Dear Calva friends: calva https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.577 • https://github.com/BetterThanTomorrow/calva/issues/2819 • https://github.com/BetterThanTomorrow/calva/issues/3185 Now you can configure output destinations as an array of destinations, so you can e.g. get results both to the terminal and to the repl window. You can also configure output to go to files. In combination that means you can have results both to the terminal and to a Clojure file, and stdout stuff can go to a file or to the terminal + a file. See https://calva.io/output/ for details. I am hoping this will help people avoid the repl-window for any output. And this should give us more freedom around how to design defaults, repl input, and so on. Let me know if you try it! 🙏
Hey, sorry, I think I missed the whole conversation on this topic. Why did calva.outputDestinations defaults change? And why is it "no longer(?" advisable to use repl-window for any - or every output? Thanks!
The repl window tries hard to mimic a terminal prompt behavior and fails doing so good enough. There are performance problems and other kinds of problems with it. A maintenance nightmare. I’d like to have the option to one day retire it completely, and that makes it a bad choice of default.
what tempted you to use a repl window rather than a terminal originally? I think it’s going to be a bit of a struggle for those of us who are used to the REPL window workflow to migrate to a terminal
The timeline (or order of things, rather) is: Originally Calva used a terminal for both output and input. Then we used a repl window web view (this move was because we wanted Paredit support for the input). Then a repl window file. Then we added options for output, output channel, repl window, and terminal. Then we added a web view output window option. Then we changed the defaults for output. Then (yesterday) we added the option to have multiple output destinations per category of output, plus the option to use arbitrary files as destinations. Every time we have changed things it has been either because we saw an immediate improvement opportunity or because we had discovered limitations and churn. E.g. the repl window webview seemed like an excellent idea until we hit limitations and bugs in VS Code’s webview support that the VS Code team wasn’t planning to fix. Depending on what you appreciate about the repl window, an option may be to use one or more files instead. Maybe in combo with the terminal or the output view. If you fancy the repl window as an input option, a regular file may still be an option. (Not that I have tried it, so it may also not be a viable option with the same regular file for both input and output.) Perhaps most important for you, @jimmyssj3: Don’t fear that retirement too much. You can keep using the repl window. It’s not going anywhere anytime soon. And only if we develop a new input solution with some decent editing support will I consider starting any retirement action.