language servers tend to do static analysis and are not evaluating anything, single or multi line

Those are types coming from the rust language server running the rust type checker, clojure is not statically types and does not have a type checker (core.typed exists but cannot type all clojure code and is far from universally used)

clojure-lsp can deliver linter style warnings for some known cases, but not universal

Ok, so there is no way to print mult line hints (I see those can be evaluated multiline via conjure+repl) but hints are not multiline

secondly, this evaluates single line

#CK143P6D7 is probably the better place to ask that since evaluation has nothing to do with LSP.

(FYI: I deleted your second top-level post since you asked that question again here in this thread)

the LSP protocol supports inlineHints, it's exactly what you see with rust (that comes from the rust LSP), but I never found anything useful to show for Clojure, and as @U0NCTKEV8 mentioned I don't know a reliable way to get types without a repl session

One way is to use Conjure to evaluate an expression as a comment, there is a specific command or you can paste the result from the register (e I think). Then it is more permanent that the transitory inline eval result. Conjure has the REPL log to see the eval history Or https://practical.li/clojure/data-inspector/portal/ can be wired up to listen to all evaluation results so you can have as much history as you like

@U03E8B3CCTV Clojure does not have "types" so there's no such thing as type hints like you've shown here (multiple times).

@U04V70XH6 I should been more clear. I wanted the eval output as in 4 in 2+2=4 in clojure. That is already there in the picture I posted. I just want it multi line just like the rust picture.

That is not eval output in the rust screenshot

And lsp, as has been mentioned over and over in this thread, the language server protocol is not responsible for evaluation

And a language server that serves up static information or a clojure process that does evaluation both just provide information to your editor, and your editor is responsible for how and when it is rendered, which is why everyone has been pointing you to #CK143P6D7 which is apparently the editor you are using

yes, thanks. I should have been more clear.

I will ask in #C03S1KBA2 as suggested

#CK143P6D7 NOT #C03S1KBA2