It’s that way because output was breaking the structure of the Clojure document of the REPL Window. There are now two additional output options that you can consider that do not print output prepended by semicolons. See https://calva.io/output/

So it's no longer possible to have it print to the repl window without a semicolon?

I'm kinda used to having the evaluation output in the Repl window being in color and never use the output tab. The jack-in terminal shows my projects automatic evaluations.

It’s no longer possible.

oh noo 😞

How was it breaking the structure ?

It caused too much trouble. See if you can use the terminal output option or a combination of the repl window for result and the terminal for output.

No I can't, the project I work on has constant processes running in the background that print to the terminal window

It breaks structure if the output contains unbalanced brackets, or unmatched quotes. Or some backslash and probably some other situations.

The output Window is something I never use

Mhh I clean my repl window most of the time when it goes over +/- 500 ~ 1k lines

Not sure how the constant process prevents you from using the terminal output destination?

Let me make a screenshot

We are probably going to retire the repl window as an output destination entirely at some point. It has performance problems that are a bit too involved to fix.

Mhh, imho that kinda sucks

Well, we will not retire it until we have some alternative that doesn’t suffer the performance problems.

The terminal window below contains process logging from the project

this is semi continous

not an option for me to see my repl evals

Well, the terminal output destination does not print into the Jack-in terminal. It’s a separate terminal. You can display it in split view or drag it into the editor area.

you mean the one on the left here?

just pulled it into view

Doesn't really feel intuitive to have the result of a repl evaluation print in a window other then the actual repl to me.

Like so

Doesn't that defeat the actual use of a repl in the same window?

Not following.

Read Eval Print, to me means type something, evaluate it and print the outcome? If the print isn't in the same window you can easily overlook it? Plus adding another window/tab means having more to monitor? Sorry if I sound like an ass, just very used to the way it was

Will try the way you have it, my output window is not in color nor does it autoscroll, is that a setting?

oh my.. this is really confusing. the repl doesn't always give a new input prompt after evaluation

That’s a bug if so.

I didn’t even know there was a log file for the Output channel.

If you reevaluate something above your current cursor location you do not get a new prompt. It does when sing repl-window as output

sing = using

I’ll have a look at that.

Or, actually. If the new prompt would look the same as the current prompt, we skip printing it on purpose.

Auto Scrolling is afaik controlled bu VS Code button, see image.

Mine was off by default..

I recommend trying with the terminal as the destination instead. It autoscrolls more intuitively.

how do you get the output window in the editor area, I can only seem to get the log file there?

The output channels lock scrolling when you click somewhere in them.

You can’t get the output channel in the editor area. But the with the terminal output, you can.

terminal window is not an option. for me still it is counter intuitive to have your repl eval output not below the code you evaluate (unless you ofcourse evaluate it from some other file then the repl window)

Same image as above ... menu shows 'Open Output in Editor'

(read-only tho)

Thats what I used

it doesnt auto scroll for me tho

Ah, so that’s where the log came from. TIL.

So, why is the terminal destination not an option. That is totally unclear to me.

I’m curious and optimistic to try the new setup. One think I like about the repl output being in the editor window is that I can use regular vscode commands to navigate, select, and copy text/data from output. I use Cursorless, so I can say “bring” and target a specific data structure, token, or keyword from the output to fluently splice it back in to my working code. That being said I also clear the repl results regularly. (One reason is to see the top of the data, not auto-scroll). Cursive has scrolling setttings and a clear-results command for the repl that I was used to when coming into Calva

I miss that too from the other output options, @U09D96P9B.

So how do I set this to be printed to a terminal?

You can copy the last evaluation result to the clipboard with a command, @U09D96P9B. You probably knew.

Replace output-channel with terminal , @U02CX2V8PJN.

alright, will try that

Ahh now I see what you mean with terminal. I tried opening the Calva Output window before but got this error

And got confused because of this hover

I kinda agree with @U02CX2V8PJN’s points wrt REPL flow, trying the new combo now, since I miss the coloured output.

Which version of Calva are you using, @U02CX2V8PJN?

I've got the same error regarding focusing on terminal, I just wrote a new message on #calva My Calva version is v2.0.430

So, this is what it amounts to. Still, having a second output window next to a repl window is counter intuitive to me. But, I will try using it at I am missing the coloured output

My version is:

Calva version used: v2.0.430
clojure-lsp version used: 2024.03.13-13.11.00
clj-kondo version used: 2024.03.13

Very strange that it warns about terminal. I don’t understand why that happens. Will need to tale a closer look. But very confusing, I agree.

Could it be an option to have the output be printed in the repl window without the semi-colon? Disabled by default?

Could be, but I try to avoid settings in general, and if the setting means “Do not complain if the REPL window stops working” I hesitate even more.

Fair point 😉

When my REPL window stopped formatting due to some lingering extra characters I just killed the repl and jacked in again. Not optimal but worked for me.

As maintainers we at some point have spent enough time helping users with certain problems, and with trying to mitigate the problems.

I fully understand and agree, I'm usually quite adaptive!

We are planning to introduce a dedicated Output Window. Hopefully we can create an experience that suits most devs. Even if we will not be able to do the rope trick with making something that suits all.

Same here, understand and agree

Thanks. I think you are being very reasonable. 😃

Isn't that what being colleagues in Clojure is all about?

This is not Python

Yeah, I think it is. Very happy to be part of this particular community!

I created a discussion in the Calva repo to continue https://github.com/BetterThanTomorrow/calva/discussions/2462

hashp #p outputs are destroyed by this

@U04M0JEU88Z you mean by the semi-colon? Have you tried the terminal output destination?

I have been trying the terminal output since yesterday and even though I like the terminal like output I have now been frustrated more then once due to me questioning why my evaluated code in the repl gave no output...doh:melting_face:

This will need getting used to 😉

Same here @U02CX2V8PJN. I’ve learnt to expect the result being printed there. Maybe we could print something like “Results printed to <wherever>“…

or move the repl input to the same window?

I now print the result into the REPL, everything else into output. It is not as good as colourful everything in REPL but as I also suffered from REPL losing formatting due to rogue characters this is a compromise.

Regarding the option you suggested to allow to opt-in on stdout being printed raw, I am starting to lean towards doing something like that. It will be opt-in and be on your own with it , but I think that while we do not have an alternative that is similar enough, we could allow it and be clear about that it is temporary. Or something.

My thinking goes along the lines that result is crucial and in REPL, everything else is details and can be in the output.

I would maybe do that too right now, if I weren’t dog fooding, @U0267SNCPEY.

Regarding REPL in same window, @U02CX2V8PJN, the coming output window will probably not have that. We are too scarred from having tried to provide that in different ways for 6 years now.

Isnt it weird that Exceptions get printed in both windows but ytou can only open (click on) the stacktrace in the repl window.

That is why the exception is printed to the repl window regardless. It’s the only place we have clickable stacktraces.

Hmm... imho a repl should have input and output in the same window. If I start clj or bb from command line I get the same

I have obviously been of the same opinion, and still am partly, for six years.

You could actually do it like that with Calva too. Start clj and the repl from the command line and connect calva to to that repl.

It's pity VSCode doesnt support having a split window for just 2 tabs. If I do that all other tabs suffer the same fate hehe. Kinda hard to explain, ill make a screenshot.

VS Code window/tab/panel management is a mess. It is strange that they allow it to be like that.

I usually split my workspace over 2 or 3 main tabs with files on those tabs. If I put the output and repl window on the left split like it is now the other files on those tabs cant be the full tab and are split too. Thats annoying like poop coming to quickly

I'd be happy with an option to remove the semi-colon from the repl-window and live with potential issues. but thats just me

Is it possible to get it to output to both the output window and the repl-window?

Is output window here the output terminal?

The Calva Output fake terminal and the repl.calva-repl output

should have been more specific, exqueeze me

That would provide feedback on repl info (even if preceded by a semi-colon) and if I would want colored output I can look in the terminal output

It’s not particularly colored in either, though?

It is for me?

Interesting. 😃

top is output window, bottom is repl window

dont mind the errors lol

I see colors here 😛

The results are colored in both. Though I don’t think that was what you referred to as it? Because results are not prepended as line comments.

true, thats only when everything goes to the calva-repl

You can print colored output to the terminal, but you will have to use ANSI escapes, which you can get from a library. The REPL window can’t handle that though, so we strip ANSI escapes there.

My question was if the results can be sent to both windows at the same time

We could consider.

That way you can have result to your repl entry

and if you need to see the colored output you can have a look in the pseudo terminal

Now you’re back at the colored output…

let me refrase

Here's an example. If I type and evaluate (= 1 1) in the calva-repl and have all calva.outputDestinations set to repl-window the result would be like the bottom tab in the screenshot correct? If I set the calva.outputDestinations to terminal I wouldn't get the result in the bottom window and it would print like the top window, correct? Can it be both? Result in the repl-window and terminal.

like this

I’m hesitant of that, but I’ll consider.

I understand, don't do this only because I asked.

It might cause performance issues?

What’s funny with your first screenshot is that it looks like the result of (= 1 1) is printed to the repl window as a line comment.

thats my fault

Hence the second sreenshot

I rather think it’s confusing.

Removed the screenshot to not cause confusion

I thought a while that we had a bug. 😃

my bad

I’m just happy it wasn’t so. Haha.

Looks like a bug. Are you connected to the repl with the terminal set as an output destination?

No

"calva.outputDestinations": {
        "evalResults": "output-channel",
        "evalOutput": "output-channel",
        "otherOutput": "output-channel"
    }

the moment you set that to terminal a wild terminal output appears

I did change the output destinations while REPL was running. Started it with the default settings

Could be that the terminal was not created when you used the command. Still a bug. Just trying to understand.

> the moment you set that to terminal a wild terminal output appears ?

As soon as I changed output-channel or repl-window to terminal a new terminal spawned

after saving the json

I think it needs that something is printed to it. Which probably happened for you @U02CX2V8PJN

Ah, so the pseudo terminal started when jacking in is not the terminal. Shortcut works only if I have at least one output destination defined as terminal.

Please report the bug to the repo, @U0267SNCPEY, as far as you understand it.

@U02CX2V8PJN, for your views on the repl input and output being in the same window. You are welcome to start a discussion on the Calva repo about it. If we have those discussions here we will have them over and over again. Better to have a URL to point at.

Sure, will start one. Am curious how other devs use the repl window

When configuring at least one terminal destination shortcut works. Issue created ➡️ https://github.com/BetterThanTomorrow/calva/issues/2461

Another nice thing in output window is that you can follow links easily. Seems like you can do this in output panel too. With terminal you can follow a link, but it pops up a security confirmation prompt… just observations

You mean URL:s?

I.e. this?

Yes

Ah, that’s true. I don’t think we can prevent it, but I think we can at least catch that it happens and say something about it to the user.

I never close anything so I guess that’s why I haven’t noticed.

And we should be able to re-create it. Please report as an issue. @U09D96P9B.

^ Something to keep in mind with the new Output Window, @U9A1RLFNV ^

As a workaround you can Pin the window, this makes closing it have a second action

Ok thanks. What is best way to re-create it atm?

I guess reload window. I’ll try that.

This doesnt work? Calva: Show/Open the Calva Output Terminal

Reload is probably the only thing that works for now. I missed that this could happen. But I think I know how to make it auto-recreate. Issue please. 😃 🙏

Ok will create issue later on. Yes reload works. (now show/open.. once dead)

You need to focus the terminal first, right? I was thinking we could add commands for clearing the configured destinations.

workbench.action.terminal.clear Seems to work, even when I am in the editor window.

But specific clearing commands as needed are appreciated.

Wouldnt mind a setting to auto-clear before each evaluation. (but could wire that up myself if really needed)

workbench.action.terminal.clear may probably clear any terminal that was last active.

This and a stably positioned REPL prompt are my top wishes for Calva. I mostly use regular editor buffers for evaluations, so it's not a big problem though.

If it was a tab (editor) when the window was reloaded, I think it will be recreated there. I don’t think we can make it be created there otherwise, but I may be wrong about that.

Maybe a command to move it? Might need to look to Joyride for this.