-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support Standard Clojure Style? #54
Comments
Thanks for creating this very interesting project. I would like people to be able to use their preferred tooling as easily as possible from Neovim. I typically use format & lint tools via the Neovim Mason package manager Clojure LSP also has format features via cljfmt and I understand that project wishes to support other format tooling (cljstyle, zprint, standard-clojure-style) There is also the conform plugin that integrated a very wide range of format tools for many different programming languages. So the decision is not if I should include this, but what is the most appropriate or convenient way to do include standard-clojure-style. I will experiment a little this week. Any other feedback or ideas is welcome. Thank you |
If this project is organised as a Neovim plugin or added to the mason registry (of linters & formaters), then let me know and I will include this as an option to the Practicalli Neovim config. Thank you. |
FYI for anyone who has found this thread: there is now a Neovim plugin for Standard Clojure Style |
Hi 👋
Standard Clojure Style is a new library for formatting Clojure code. You can see a 10-minute demo and introduction of the tool in this video from Clojure/conj 2024.
I have ported the algorithm into a zero dependency, single-file Lua library with Standard Clojure Style Lua.
The purpose of this issue to see if it would make sense to make Standard Clojure Style available to users of this project? This may be considered out of scope for this project, but I thought it may be worth suggesting.
The text was updated successfully, but these errors were encountered: