This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-21
Channels
- # admin-announcements (2)
- # aws-lambda (2)
- # beginners (26)
- # boot (179)
- # cider (36)
- # cljs-dev (118)
- # cljsrn (23)
- # clojure (150)
- # clojure-android (1)
- # clojure-austin (7)
- # clojure-austria (3)
- # clojure-canada (1)
- # clojure-dev (7)
- # clojure-dusseldorf (4)
- # clojure-germany (3)
- # clojure-greece (34)
- # clojure-nl (4)
- # clojure-quebec (9)
- # clojure-russia (30)
- # clojure-spec (38)
- # clojure-uk (3)
- # clojurescript (46)
- # clr (1)
- # core-async (2)
- # css (2)
- # cursive (17)
- # datomic (12)
- # devcards (8)
- # dirac (1)
- # docker (2)
- # hoplon (216)
- # jobs (2)
- # kekkonen (1)
- # lein-figwheel (18)
- # leiningen (2)
- # luminus (1)
- # mount (4)
- # off-topic (2)
- # om (15)
- # onyx (1)
- # parinfer (1)
- # pedestal (2)
- # planck (26)
- # reagent (98)
- # spacemacs (6)
- # specter (19)
- # spirituality-ethics (54)
- # untangled (22)
- # vim (24)
- # yada (4)
Okay. So I got the javascript debugger working, but it’s separate from the repl and doesn’t speak Clojure. Any ideas on how we can integrate the two?
would Dirac help @seantempesta ?
Dirac is for Chrome, right?
@seantempesta: yes :thumbsup: but you can connect to Dirac REPL from Cursive. Havn’t attempted any debugger integration yet.
@cfleming: another feature request - a Clojure specific unified fuzzy search. Not the search everywhere of IntelliJ (I'm aware there are issues integrating with it). Unified searching for symbols/namespaces/keys/files.
@cfleming: a lot of times i find myself mistakenly launching the search ns, when i wanted to search a symbol, or vice versa.
@moizsj: One thing I have been considering is to have a keypress to switch the search type when there are no results. IntelliJ already does this for some cases (I believe it switches to a file search if a class search doesn’t work well).
@cfleming: but wouldnt a unified search be just easier? I dont have to pause to think what type i want. And in case i pick the wrong type, a further keypress would be needed.
Possibly, yeah. I’m a little worried about implementing something that is basically search everything again. A better solution might be to make that extensible and send them a PR.
@cfleming: of course the individual type specific searches would still have value and be relevant
@cfleming: you may be correct from an implementation perspective. but from a user perspective, I'd definitely prefer unified (as one of the search types). you've already implemented 3 of them, would it be hard to merge them?
No, it wouldn’t. But what I mean is, that’s what Search Everything is supposed to do, the issue at the moment is that it’s not extensible. So I’d rather make that extensible so that you could just use that.
I suspect if I send them a PR they’d accept it - I’ll mail the developer in question and ask.