Clojurians Log v2

I think it should work. What’s your settings for output destinations?

"Unchanged", I would say .... But not sure ...

the same has happened to me

I check.

I see evaluated code in the repl but not the output

I see "nothing", except the message of " jack in done"

in my case, I was missing

"calva.outputDestinations": {
    "evalResults": "repl-window",
    "evalOutput": "repl-window",
    "otherOutput": "repl-window"
  }

I just tried codespaces for the first time. Output goes to the Calva output terminal as per the new defaults. Have you evaluated anything, @carsten.behring? I’m not sure about what your expectations are.

see screenshot for a "Blank" repl output. whatever I do it stays blank,

Is Calva configured to send output to the REPL Output view?

Maybe I am "confused", as executing "jack-in", does snot "open any view" (any more)

and evaluating code "shows nothing"

The confusion is very much on Calva’s part, it’s a weak spot in the Ux, for sure.

But you still haven’t answered what your output destinations settings are 😃

so there is no "auto open result output destination", eventhough the setting is "enabled"

I see the Output terminal opened, so maybe that is your output destination?

It’s the default output destination, after all.

yes, but it is and stays "completely blank", even when evaluating.

Do you get inline results when evaluating?

Now it kind of works... But I miss the "auto open" after jack-in. "in the past", sucessfull jackin always made a "big visual change" of UI. now it seems that if "Terminal" tab is not focused by chance, sucessfull jack-in makes no visual change

I see, there are now more "auto open settings"; but disabled by default.

Yeah, I even disabled auto-opening of the inspector on connect, so very little visual feedback that the connect is done. The REPL button turns ember.

But you now see evaluations in the output terminal?

Yes. That's at least "new" to me. For me a succesfull connect always changed the UI a lot, as the "view auto-opened" (in default, at least)

+ now the evaluated code is "echoed", new as well ?

Yes. Also a new default.

https://clojurians.slack.com/archives/C06MAR553/p1776009597263819

ok... I think nothing is "Broken" on Codespaces. Just that the "new default" shows very little UI change "on jack-in", which I interpreted as "Nothing works".

In combo with all the output destionation confusion. I wish that weren’t so, but I guess it is a prize we pay for developing Calva in the way we do.

Question. The REPL Output view you have on your screenshot. Was that something you opened, looking for feedback about the jack-in?

yes... I guess so.

I was not really aware that "output" is in "terminal now" (depending on settings, at least)

My plan is to eventually be able to make that output view the default ouput view. But as long as I can’t place it in the sidebar, I can’t really use it myself, so it makes for a strange default.

Maybe it's just "habbit"- I was used to "see auto-open" of a a new view happening always after jack-in. This was for me the "signal" of "jack-in finished". Specially I work often containerized environments, so it "often" downloads dependencies "on jack-in" So I was used to "wait for the autoput window opening" as the "signal" of "done".

Seems natural that when the behaviour of an app changes, it may seem like something is broken.

Happy to hear that @pez, thanks! @seancorfield Being just another editor window fits well with my workflow, opening/closing it, moving into/out of it (don't need another set of shortcuts just for that), copying from it, pretty printing, editing the output there directly, etc.

I switched over to the terminal output for all destinations ages ago so I'm curious what you prefer about repl-window?

It has been discussed many times, but always scattered. And mostly in this channel. I’m in no hurry to deprecate it. Especially now that it’s not the default, I hope we can have less of maintenance troubles with it.

Agreed, unless someone knows a good way to do that with terminal output, I find it really easy to copy and select different things in repl-window. The same paredit methods I use in Calva work there. I don't want to scroll through powershell for a huge map output. I'm more curious what could be better about the terminal?

@crimsonhawk47 It's a pseudo-terminal for Calva output. It's not Powershell or bash.

Still not the most convenient for navigating and selecting. I miss that from the repl-window file.

I guess with my Portal usage, and being able to navigate/copy values there -- and being able to copy the last Calva eval to the clipboard (`ctrl+alt+c ctrl+c`) -- I only use terminal for a quick sanity check of values. Before I switched to terminal from the repl-window, I used to keep the repl-window hidden anyway 🙂

Copy last results is what I use to get the results into a file that I can navigate with paredit.

I think it's interesting to see what different workflows other people have. Since I've always been in the do-not-type-into-the-REPL camp, I've tended to rely on inline eval or Portal for viewing results and almost never used the REPL output window, even in its original incarnation. For me, having it show up in a "terminal", at the bottom of my screen along with my actual terminals (bash) and the Joyride output, and anything else VS Code decides to throw down there, is sort of a useful bonus...

Copy last and Portal would help me use the terminal. I didn't think of my workflow as typing into the REPL, more it's just there from previous eval, and I copy from it as needed. I could see why Portal and copy last would eliminate that.

Personally I find that the different syntax highlighting between the repl output window and the terminal disorienting

Yeah, it's not about typing into the REPL, just that it's an editor window so all the muscle memory from working with 'proper' code carries over. The only time I'd prefer a tool like Portal over it is if the output is just too unwieldy (large) and you need some way to toggle (even that can to an extent be replaced by "folding" in the editor). But in terms of being able to move around the data with all the usual shortcuts (moving by sexp, in/out – what @pez said: using paredit), all the tools available to search and replace, etc. Hands down a better experience. I usually have two editor windows open side by side. Only when I need the repl window, I open it as I would any other file, in either of the two.

The sweet spot for me would be something like the https://code.visualstudio.com/docs/python/run: it's still an editor so you get all of the syntax highlighting and navigation you're used to, but it's also terminal-shaped in that you have a text input (not that I use it) and a series of outputs. The notebook editors also do some of the stuff that tools like Portal do, in that the outputs can be interactive or navigable, but they also will show a decently-sized preview of an output (with an option to expand/navigate if the output is too large). One of my pet peeves with Portal/et al is that they tend to push me into a navigable UI which makes it hard to just scan it quickly without clicking a bunch