@steiner3044 are you familiar with tools/plugins that will automatically close your parents/brackets for you? That might help keep your code parsable for completion suggestions
nope, the configure are all on the image I uploaded
@brandon.ringe With this https://github.com/clj-kondo/clj-kondo/pull/1147 fix we now show correctly the range for textDocument/documentSymbol
.
About the returned symbols, I'm thinking that the first element (always the current ns/file) does not makes much sense, what about showing only the functions/vars?
For example, in emacs we show unnecessarily the ns again:
I think file
-> function
it'd be enough, instead of file
-> my-ns
-> function
WDYT?
That sounds good to me
Can try it out at least and make sure it looks good
Ok, I'll open a PR for you to test it, ok?
Great!
:reviewplease: https://github.com/clojure-lsp/clojure-lsp/pull/281
1👍@steiner3044 check out https://thoughtbot.com/blog/writing-clojure-in-vim which includes some helpful context around editing lisp/clojure code. One useful tool is to install Paredit (or a similar tool) which will help you keep balanced parentheses while adding, editing and deleting code
:clojure-lsp: Released https://github.com/clojure-lsp/clojure-lsp/releases/tag/2021.01.26-22.35.27 version of clojure-lsp
improving memory usage 🎉, let me know if you find any issues.
I see one application from you for January 3rd, we definitely got it; we just don't send full feedback until we've voted on a batch, so yeah you should expect it close to next quarter :)
That's exciting! thank you @lvh !
🎉
2@jakub.zika-extern It's not a conflict in the sense of broken per se, just that it wants to use one or the other, so, suddenly CIDER disappeared on me
(also I am from the American Midwest so please keep in mind that "the other day" can mean 6 months ago)
1😁