This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aleph (8)
- # aws (2)
- # beginners (36)
- # cider (35)
- # cljs-dev (157)
- # cljsjs (3)
- # cljsrn (5)
- # clojure (97)
- # clojure-dev (5)
- # clojure-gamedev (3)
- # clojure-italy (27)
- # clojure-russia (11)
- # clojure-spec (19)
- # clojure-uk (39)
- # clojured (6)
- # clojurescript (87)
- # clojutre (4)
- # community-development (35)
- # cursive (8)
- # datascript (2)
- # datomic (14)
- # dirac (8)
- # duct (3)
- # figwheel (13)
- # fulcro (22)
- # graphql (20)
- # jobs (1)
- # london-clojurians (1)
- # off-topic (55)
- # onyx (3)
- # parinfer (3)
- # protorepl (39)
- # re-frame (3)
- # reagent (26)
- # ring (7)
- # ring-swagger (2)
- # rum (1)
- # shadow-cljs (107)
- # spacemacs (8)
- # test-check (4)
- # unrepl (3)
@lee.justin.m do I have to worry about other plugins overriding some of the keyboard shortcuts? does the latest installed plugin "win"?
I still do not fathom why does the docs say "ctrl alt <key>" yet means "hold ctrl + comman, release, then press <key>"
Well if anyone cares, here my silly addition to clojure development in atom 😂 https://atom.io/packages/online-clojure-search
Ping-ponging back to proto-repl after using for awhile, going back to cursive/intellij, and returning again. This time I plan on cataloging the little things that bugged me, and seeing if I can help get them fixed. First thing I ran into was that the actual REPL window does not auto-scroll. Is this a known issue?
@dave.dixon It does auto-scroll -- most of the time... But if a panel pops up at the bottom and hides the current last line (e.g., doing a find), then it stops scrolling.
I tend to clear the REPL regularly so the last line is always further up the screen (or simply not bother to even look at the REPL since I never type into it and generally use the inline result displays in my source editor.
Similar to @dave.dixon Is it only me getting this behavior - https://github.com/jasongilman/proto-repl/issues/295
@seancorfield Right, just verified, and that rings a bell. Any idea what causes that problem? It's not a big deal, just one on the list of the "thousand cuts" that eventually bled me dry the first time.
Is any form of "jumping to definition" provided by proto-repl? I see a command for jumping to the source of a Var, but it doesn't work for me.
it doesn’t work unless you are using clojure and are connected to a real clojure repl
so should I just start a repl with proto-repl first thing as I load a clojure project, if I want this feature working for me?
you definitely need a session going and i’m pretty sure that session has to be a real clojure session, not an nrepl session and probably not a cljs session
so which proto-repl command should I invoke to get going? it's not really clear to me from how the different repl commands are named/documented
@matan I generally use
Proto Repl: Toggle which is cmd-opt-l or ctl-alt-, l (that's an L) which starts a Clojure REPL based on the first project in your workspace.
Or you can open the project's
build.boot file and do cmd-opt-L or ctl-alt-, L (Toggle Current Project clj)
Only one thing, in my Atom, all keyboard mappings do not include the
alt key. Why is it mentioned so much as if
alt is part of the keyboard combination?
oh well, thanks a lot, I'll use the toggle command, though I've no idea why it is called like that
It is a weird name. After all, when you have a REPL open, "toggle" doesn't turn it off 🙂
@matan @lee.justin.m I'm able to navigate to vars when connected to nREPL, for clj at least. Haven't tried with cljs. The only minor irritation is that when using the boot REPL, boot takes over the classpath, so navigating to a definition in your project takes you to boot's temporary copy of the source file. Using
lein repl navigating to a var takes you to the file in your project.
Yeah, I went poking around the proto-repl code to try and understand the boot issue, and I can see why it wouldn't work with cljs. It's leveraging machinery from the
clojure.repl namespaces, metadata on vars, and so forth, and evaluating it in the REPL. I don't know if you could make that approach work in CLJS.
for some reason understanding the repl issues is just beyond me. i think i have dunning-kruger on this issue because it seems like you just need to port a few simple commands back and for and it’s all text
I think Stockholm syndrome is a better fit for people having chosen a clojure dev environment