Fork me on GitHub

@ericdallo I am doing a maintenance sweep of an app. It is so useful to see those reference counts on vars. Especially fun when the count is 0! Thanks for an awesome feature!

🎉 2

Glad to hear it! Thank you 💜


I concur. The reference feature convinced me to start using LSP, as I was trying to understand and refactor a code base that was new to me (and helped me delete lots of redundant code).

🎉 1

I love deleting unused code. Such a rush. The fact that clojure-lsp distinguishes test vs non-test usages is very cool too. Oh, the only place this is used is in a test? Huh. Delete, delete, delete. 🎉

😂 1
🔪 1
Drew Verlee21:02:14

Is there a way to surface LSP warnings and errors in a session log? Legacy apps might have lots of issues (e.g unused namespaces) that aren't worth trying to address while working on a new feature. But it would be nice to see if a chunk of work/session/git diff introduced an issue.

Drew Verlee21:02:35

maybe it could be surfaced to tooling similar to how doom-modeline shows lsp info. Like a even darker red 🙂


no, there is no such feature, for that we would need to integrate with git or something, it seems too much specific


for now you can disable diagnostics for sepcific namespaces

Drew Verlee21:02:19

Thanks Eric, i'll think about that. I agree it such a feature should be opt in. But i suspect a lot of users would find value in it, git being the industry standard and the issues i present would seem to be a common one. If it isn't i'm curious what people are doing to solve this issue. I believe i can create the tooling for this already just by running the linter on the previous commint and current code and taking the diff. I mean, i know i can because we have a github action that must be doing that somehow though i'm currently not seeing how it gets the diff. 😆


I think the action run and just show warnings on files that were changed?