Compilation errors in "Output" panel instead of "Problems" panel

[nigelgilbert]

@avli
How do you feel about putting the eval compilation errors in the "Output" panel, instead of the "Problems" panel?

This is how proto-repl displays compilation errors, and I think it is more convenient, since one doesn't need to click or hotkey to the other panel for feedback.

From a workflow perspective, it just feels clunky to me to have to change panels to see all the Repl output. I don't want to move my cursor, and I don't want to memorize the hotkeys to switch between the Output and Problems panes.

Moreover, from a logical perspective, should the repl compiler errors even fall under "Problem", anyways?
The blank Problems window reads: No problems have been detected in the workspace so far.

The eval compilation may fail due to issues that are not directly related to your workspace, your code, etc. For example, when you eval a function (foo) without first evaluating (defn foo [] ()). Therefore I think that categorically speaking, Output may be a more fitting place for the repl compilation errors.

[fasfsfgs]

As an user, I agree with this change as well. That's what I was expecting when first using this extension. I actually used it the first couple weeks without even knowing the 'Problems' tab was used.

If one day we pick up syntax errors on the fly, maybe 'Problems' tab would be a good place to put them.

But for compilation errors, I vote to put those in 'Output' panel.

@avli I can make this change myself if you agree.

[nigelgilbert]

@fasfsfgs

If one day we pick up syntax errors on the fly, maybe 'Problems' tab would be a good place to put them.

True.

[fasfsfgs]

I talked to @avli and I'll make this change. Compilation errors are going to the OUTPUT panel.