This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (25)
- # boot (14)
- # business (1)
- # cljsrn (2)
- # clojure (180)
- # clojure-korea (14)
- # clojure-russia (8)
- # clojure-spec (9)
- # clojure-uk (17)
- # clojurescript (110)
- # cursive (14)
- # datomic (18)
- # emacs (23)
- # events (4)
- # garden (7)
- # hoplon (44)
- # lein-figwheel (1)
- # liberator (4)
- # london-clojurians (1)
- # om (10)
- # om-next (2)
- # onyx (22)
- # protorepl (60)
- # re-frame (36)
- # reagent (11)
- # ring (10)
- # yada (5)
@kzeidler: Is there any reason to not just use the clojure layer? It's quite good and full featured.
@ewen since reload dependency namespaces is difficult, how about add a on-jsload function? I can have rerender React in that function. otherwise reload the namespaces (except the main namespace) will not cause the rerender.
@doglooksgood I will think about that, having a way to trigger a rerender on file load would be very useful
paredit users, does anyone use M-; from paredit. Seems very pointless function paredit-comment-dwim. I'm trying to find a conveinient way to comment in emacs terminal mode, kowing that
C-; is not possible witin a terminal. Just trying to unbind this paredit command and rebind it with my function, but its not as straightforward as it sounds.
ahh so its a known problem http://stackoverflow.com/questions/16605571/why-cant-i-change-paredit-keybindings as previously recommended here on this slack channel by @doglooksgood (I think) there are alternatives to paredit worth to try. Im off to explore 🙂
yes Im giving parinfer another shot as we speak, remember last time I was bit shorter on time, I try lispy too while Im at it
@doglooksgood how do you make a new-line in parinfier. Also wondering if parinfier makes sense if Im not using evil mode?
ahh one needs to make () or  first before sending it down, took me few mins to realize this, interesting!
make a newline by simply pressing enter, you will get something like this:
When you type something at newline, the close paren will move down.
(foo bar) |
(foo bar baz|)
ok, what you show there in your foo bar example, do you have Parenfier:Paren or Parenfier:Indent set on?
basically, you'll always use Indent mode. the Paren mode used for 3 case: 1. the parens is unmatched in the code, with Paren mode, you can fix parens. 2. you want to change the function (for example, foo -> balabala), you have to switch to Paren mode at this moment. otherwise your code struct may change, because Indent mode will adjust parens by indentation. 3. you want to wrap an expression, the reason is same to 2.
ok, that is totally alien for me coming from paredit. But sounds like Paren mode is like turning off paredit mode. It would be nice if you had a bit better documentation, just a bit more. So I hope you forgive my questions 🙂
If you enjoy the feel of parinfer and want to know the detail how it works. there's a home page of parinfer: https://shaunlebron.github.io/parinfer/ I think this can help you