I just pushed parstager 1.0.0 to make it work with editors that trim whitespace.
Been using it for a while, and I think it solves the collaboration issue. Funny I didn’t think of it before.
Sometimes I’ll accidentally save clojure files with only parinfer changes. Running parstager cleans it up quick.
And when I’m reviewing small changes in a large clojure file, the diffs are huge until I run parstager, and it restores the formatting of all top-level forms I didn’t change.
So, almost 10 years later, parstager fixes parinfer on teams. Has anyone else been using it?
I'm having a lot of trouble getting up to speed in regards to code navigation/code overview in nvim in the quality I have in IntelliJ/Cursive.
I was on nvim/conjure/parinfer-rust, but switched to Cursive for its code navigation
yeah, fuzzy search for all known symbols or namespaces, and navigating java libraries, I don’t know how to do these in nvim
For me it's the lack of search pinning that really hurts. I want to refac an fn that is called by fns that are called by fns. Keeping track of something like that is manageable for me in Cursive, but I haven't found a good way to do it in nvim
And there are nicks and cuts all over, like missing the searches you mention, and stuff like Telescope/LSP finding irrelevant results (like source maps "using" CLJS function, and therefore ending up in a "find references" search result)
I think it should run before git status or git diff, but git hooks only exist for write operations
Ah. Well, you could glue them together in a tiny utility script?
I'm going to try some tiny script that fits my workflow, anyway
I just discovered you writing this. Have you integrated parstager with a script or something for your work? Or do you run it manually?
The automatically-indenting-a-whole-file thing is a big turnoff for me, but I love Parinfer otherwise 🙂
So this could be my savior!
nothing automated, yeah just manually running it, just reactively as a first step before reviewing changes to commit
Alright, thanks 😊
I use git commit --p almost exclusively, btw, rarely use diff or status. So I can maybe git hook onto commit.
oh cool, I always use git add -p, maybe I should use that instead. but yeah it’d be easy to wrap that in a script
what editor are you using btw
nvim for small, generic text edits, Cursive for general Clojure coding. That's how it's been for many years. But I'm trying to get nvim to a state where I can comfortably do Clojure code in it, so I'm trying out gpanders/parinfer and doing a lot of other configging 🤓
Awesome. It's been some time since I've used parinfer, can I ask what editor(s) would you recommend using parinfer with these days?
My daily driver for Clojure is Sublime Text with this plugin for Parinfer: https://github.com/oakmac/sublime-text-parinfer Package control: https://packagecontrol.io/packages/Parinfer The plugin supports Indent and Paren Mode (ie: no Smart Mode), but I don't really notice the difference. I am in Indent mode 99% of the time.
I mainly use eraserhd/parinfer-rust in neovim (with conjure for repl). It messes up indentation sometimes when inserting an open-paren, and I lose my undo history fairly often.
I also use Cursive when I need good code navigation features since it's really good at finding usages and opening Java sources.
I haven't noticed any problems with Cursive's implementation of Parinfer, but I use it a lot less.