This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-01
Channels
- # adventofcode (1)
- # bangalore-clj (1)
- # beginners (8)
- # boot (47)
- # cider (6)
- # cljsrn (3)
- # clojure (155)
- # clojure-brasil (2)
- # clojure-china (3)
- # clojure-conj (1)
- # clojure-hk (4)
- # clojure-korea (36)
- # clojure-russia (38)
- # clojure-spec (53)
- # clojure-taiwan (1)
- # clojure-uk (14)
- # clojurescript (70)
- # clojurex (9)
- # component (2)
- # cursive (20)
- # datascript (19)
- # datomic (39)
- # defnpodcast (1)
- # events (5)
- # figwheel (2)
- # hoplon (81)
- # incanter (2)
- # jobs (7)
- # juxt (3)
- # klipse (1)
- # leiningen (1)
- # luminus (15)
- # mount (1)
- # off-topic (21)
- # om (5)
- # om-next (2)
- # onyx (19)
- # pedestal (2)
- # proto-repl (1)
- # proton (5)
- # re-frame (19)
- # reagent (4)
- # rethinkdb (2)
- # ring-swagger (6)
- # rum (13)
- # specter (6)
- # untangled (4)
- # yada (1)
So I actually still use parinfer, but it does indeed drive me nuts sometimes. I’m still planning to try to create something like it which is less intrusive and more predictable.
What I like most about it is that I can do line-based operations (delete a line, duplicate a line) without thinking about parens. Probably the best thing to do is just to customise those actions to fix the parens up afterwards.
@cfleming it's not great at all. with paredit you can be certain that about what will happen when you press a key combination. parinfer is on a controversy itself, even if you add paren mode to cursive, it still slows down typing.
@saeidscorp Paredit is also deterministic, that’s an important part of its design.
I should also point out that the Cursive implementation has problems which are not inherent to parinfer itself.
For example, cutting and pasting doesn’t work well because IntelliJ tries to smartly indent when you paste, which doesn’t help things.
@cfleming will paren-mode be eventually part of cursive? :thinking_face: do you have any plan?
@saeidscorp It’s fairly easy to add. I deliberately didn’t add it because I don’t like the fact that you have to switch. My plan was to try to work out which mode to apply automatically, like this: https://github.com/DogLooksGood/parinfer-mode/blob/master/HOW_TO_WRAP_SEXP.org#more-ideas
CompilerException java.lang.IllegalStateException: Alias foo already exists in namespace something.bar-test, aliasing production-code.foo, compiling ...
I expect the problem's between the keyboard and the chair but wondering if anyone's faced this?
@imre Sounds like you might actually have a duplicate alias somewhere. tools.namespace
just does a remove-ns
and a cleanup of *loaded-libs*
during unloading.