This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aleph (50)
- # announcements (3)
- # aws (35)
- # beginners (74)
- # boot (25)
- # calva (39)
- # cider (18)
- # clara (2)
- # cljdoc (18)
- # cljs-dev (24)
- # cljsrn (11)
- # clojure (166)
- # clojure-europe (13)
- # clojure-italy (5)
- # clojure-nl (6)
- # clojure-spec (35)
- # clojure-uk (263)
- # clojurescript (22)
- # clojutre (1)
- # code-reviews (34)
- # cursive (58)
- # data-science (2)
- # datascript (4)
- # datomic (4)
- # duct (6)
- # emacs (7)
- # figwheel-main (9)
- # fulcro (2)
- # graphql (3)
- # hoplon (22)
- # hyperfiddle (2)
- # juxt (5)
- # kaocha (6)
- # leiningen (33)
- # luminus (15)
- # off-topic (1)
- # pedestal (5)
- # reagent (18)
- # reitit (12)
- # shadow-cljs (171)
- # vim (5)
I'm glad my little video and your extension are bringing more people into clojure land 🙂
@jacobhaag17 , that's weird and probably a bug. Can you reproduce/isolate it with a test where you can share the code?
Here is a quick Calva user guide I've created for those new to programming at our ClojureBridge event this weekend. https://clojurebridgelondon.github.io/workshop/development-tools/editor-guides/vscode-calva.html
I would appreciate any feedback and corrections for anything I got wrong. I may remove the structured editing section and just link to the Calva paredit webpage (which is nicely written)
I also have a simplified install guide for Ubuntu, Mac, Redhat, Windows. https://clojurebridgelondon.github.io/workshop/development-tools/install-guides/vscode-calva.html
@jr0cket "Add Clojure Project to Atom" Should this be "Open Project Folder in VSCode"? It also seems backwards to me to open the terminal before opening the project? If you open the project first, when you open the terminal you shouldn't have to cd into the project folder as you'll already be there.
I seem to get prompted for a REPL connection when opening a clojure project, or specifically a file. This is why I changed the order. I am trying again on a clean machine (testing windows) to see if I get the same effect. Otherwise, I would agree the order you mention is more logical.
AFAIK Calva doesn't try to connect until a Clojure/ClojureScript file is opened. In that case, I don't get prompted for anything, but the status bar shows the attempt and eventual failure to connect. I can then follow your instructions and connect with Ctrl+Alt+V, c.
It would be interesting if the "autoconnect" feature could launch a new terminal and spin up the REPL. Of course, since there's different ways to start a REPL you'd have to define how this is done in a local config file or something. 😞
auto-connect seemed to be popping up quite a bit. I will see if its still doing the same on the other machine....
@bill.kempf we are working on a jack-in feature that will help you launch the repl with correct dependendencies and such. Scroll up in this channel and you'll find a preview VSIX file with jack-in enabled. (It is not a release candidate, because lacking some key features, but works for plain projects.)
@pez can comment. There may be a reason you get popups and I don't. But I've just verified behavior on my machine.
ctrl+alt+v e it will evaluate the ”current” form. Be it before, under or after the cursor.
Maybe also mention that forms directly inside a
(comment) form will be considered top-level by the Evaluate top level form commands. I (ab)use that feature a lot!
(comment), yes, had some fun with that in CIDER too. I switched to
#_ for commenting expressions personally, but useful to include. Thanks
Probably missing something, but is there a keybinding to toggle comment / uncomment a line with
;;. I use
C-k C-c but it only seems to uses a single
Single quote is typically used for a comment at the end of a line of code. Double quote is used to comment out a whole line or a comment line. So usually used as:
;; This is a comment on a line by itself
(def mol 42) ; A comment of a particular line
Its part of the Clojure style guide, but as with all things is open to interpretation 🙂
Thanks everyone for your help. I'll let you know what sort of feedback we get from the students this weekend and will go see if I can add anything to the official docs early next week.
I have made all the changes to the guide and a found a few extra things to add for Windows. I thought I had hit a block on windows until a config button for the built-in terminal popped up and let me change to GitBash shell (I had problems getting Leiningen working on Windows 10, wouldnt do the self-install) so installed the
lein script to run in GitBash.
I am not seeing side-effect output like
println in the REPL window.
printlin does return
nil as a result inline
I dont know what is standard keybindings for VScode or Calva... yet. I should know more by Sunday 🙂
The side-effects thing is a known problem. It works in the new repl window (testable with that vsix file a few screens up).
Thats okay... it all works in the repl... Just testing out the experience now it all works 🙂
About the keybindings. Maybe not instruct to use
ctrl+k ctrl+o. On my machine
ctrl+k is pretty destructive. 😃
Yes, may have to duplicate instructions for Mac and PC (`cmd` vs
ctrl), but this is same with other editors too...