This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-20
Channels
- # aleph (2)
- # announcements (4)
- # aws (3)
- # beginners (141)
- # calva (9)
- # clj-kondo (1)
- # clojure (3)
- # clojure-boston (2)
- # clojure-brasil (1)
- # clojure-houston (1)
- # clojure-italy (4)
- # clojuredesign-podcast (1)
- # clojurescript (22)
- # cursive (2)
- # data-science (1)
- # emacs (26)
- # fulcro (22)
- # juxt (1)
- # off-topic (28)
- # onyx (3)
- # pedestal (4)
- # reagent (10)
- # reitit (6)
- # shadow-cljs (9)
- # spacemacs (2)
- # tools-deps (29)
- # yada (1)
Is there a reason Paredit’s join
and raise
fns aren’t supported? There’s no reference in the Calva Paredit keymap, and I see some commented-out lines in calva/paredit/extension.ts
.
Right, so maybe I have some time now. @kingmob, the reason is that Calva uses paredit.js
in the editors, and it does not have a very rich set of Paredit features. For the REPL window we have written a new Paredit ”engine”, which is more feature complete. So, in the REPL window you actually can do both join
(`alt+shift+j`) and raise
(`alt+r`). But at least the latter feels a bit buggy to me. The commented-out lines you find are a paused effort to start using the new Paredit engine in the editor.
Ah, ok. Thanks for sharing. Will the new engine make it back to the editor?
hihi 😄
@pez: I was tryin' to help someone out and we ran into this again today https://github.com/BetterThanTomorrow/calva/issues/205
any updates on what to do about this when we install clojure with the instructions on https://clojure.org (specifically: https://github.com/clojure/tools.deps.alpha/wiki/clj-on-Windows#install)?
@pez I understand that you and many others like auto-insertion of brackets, but FWIW teaching programming has long been my day job, and I don't think I have ever taught a class using a tool that auto-inserts brackets in which this hasn't been a pain point for a significant subset of the students. I also understand that the bug preventing turning this off without editing config files (another pain point) is VSCode's and not yours, but (again, just FWIW) I doubt my experience on this is unique, particularly for people teaching new programmers.