Clojurians Log v2
calva
Oh, the standard practice has always been a double semi-colon for start of a line since I started with Clojure in 2010. I think this comes from lisp too, so it's even longer practice for lisp languages The Clojure style guidesl defines ;; as a comment line and ; as a comment after code on a line Formatting tools that follow the Clojure style guide will move singe ; comments half way along the screen. Cider does this too. So a developer using Calva may cause a lot of format changes for others developers they work with.
Hi, I've been using Calva for >2 months now but for some reason I cannot get the VS Code 'Outline view' to work. Any tips?
Must be something in my code/project, if I setup a new project outline view does work. Will investigate and let you know the root cause (if I find it:wink:).
Great. Here’s hoping you find it. As I said, this is new functionality and we certainly has quirks to find.
I'm able to reproduce the issue. I've uploaded a small example to https://github.com/eu400000/Calva-VSC-Outline-Issue. The readme file has the details to reproduce the issue. Not sure if this is Calva related. I did remove the VSC 'Better comments' extension to rule that out as possible cause (no effect). Hope the example makes sense to you.
Thanks!
What’s your take on this, @ericdallo?
Sorry but I don't known how Calva outline view works, it should shows symbols of the current ns? do you know what lsp method Calva request to clojure-lsp?
Not really. It just magically appears when we hook up the lsp. 😃
But I can investigate it some. Or maybe if @brandon.ringe has the time, he is more in the know of this than I am.
I believe VS Code is using the response from the textDocument/symbols lsp request, which I'm assuming is not returning symbols or something. I'll have to look at the trace logs for this when I have time
Thanks for the repro project! Made an issue to track it here: https://github.com/BetterThanTomorrow/calva/issues/962
Yeah, probably it's what @brandon.ringe said 🙂
Hello, two months ago it wasn't enabled in Calva. But now it should work. Which version of Calva are you using?
v2.0.151. I reinstalled earlier today to see if that fixed the issue (it didn't)
(on Windows 10 btw)
That’s the latest and greatest. We have had Windows issues lately. Maybe this is one. Can you create a minimal repro that we can look at?
You mean in github (I normally use Azure DevOps GIT)?
My awkward current https://github.com/clyfe/vscode: • Sexp movement via ctrl+arrows. • Word selection via shift+ctrl+arrows. • Movement sometimes via word selection (in-sym/kw/str use) • killListForwardToClipboard used for delete, cut, or copy sexp list Should be pretty usable for folks that haven't used paredit before.
I’m not picky. 😃 But a repository we can clone that exposes the error.