This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-06
Channels
- # adventofcode (24)
- # aleph (1)
- # bangalore-clj (2)
- # beginners (196)
- # boot (148)
- # cider (18)
- # clara (83)
- # cljsrn (24)
- # clojure (210)
- # clojure-brasil (3)
- # clojure-china (1)
- # clojure-italy (11)
- # clojure-korea (8)
- # clojure-russia (82)
- # clojure-spec (115)
- # clojure-uk (130)
- # clojurescript (109)
- # core-async (7)
- # cryogen (1)
- # cursive (22)
- # datascript (11)
- # datomic (6)
- # devcards (2)
- # emacs (1)
- # garden (1)
- # hoplon (2)
- # incanter (1)
- # klipse (4)
- # luminus (4)
- # off-topic (89)
- # om (53)
- # onyx (78)
- # parinfer (9)
- # proton (3)
- # protorepl (20)
- # re-frame (107)
- # reagent (52)
- # rum (30)
- # spacemacs (1)
- # testing (3)
- # untangled (31)
- # vim (43)
- # yada (9)
I just wrote something that might interest those here. https://github.com/SevereOverfl0w/.files/commit/7e24428b70b508786f8d9931a35407763c90340c added a Unite interface to the ability to find other usages of a symbol. Works within a function/let too which is awesome. I'll probably shoe-horn it into a plugin at some point too, and attempt to add support for the location list and fzf and denite.
Maybe the denite version will be only for acid, so I can do it async and enjoy that fact.
Have you started using acid ?
Not quite yet, there is some code pending review to add autocompletion support for acid though.
@dominicm unite_find_symbol_syntax function is duplicated
Oops, yes. I wanted to rewrite without losing my progress, and forgot to delete the old one, thanks.
I'll start focusing on making acid better for extensibility and bother people to start using it instead of vim-fireplace on january..
I decided to shift my focus on making acid really a "deoplete" for async clojure plugins.
@ingvij will it support clojurescript ?
Clojurescript support is easy in principle. So I don't think it will be a problem to handle cljs, as long as sessions are handled correctly.
For me clojurescript in vim has been a pain point.
Acid is designed to be asynchronous (thus, nothing blocks your editor). It is also designed to be extensible
It means that adding new functionalities such as better refactoring is simple and non-blocking 🙂
@zamaterian Rather — It should be simple. Figwheel has been a real pain, but now works 100% which is great. I understand the underlying nrepl mechanics fairly well now, and I will try and make sure to guide Acid in a direction that (to the best of my understanding) will make Clojurescript a simple process.
I'm very torn on whether or not we should be mirroring the :Piggieback
behaviour of fireplace for example. As it:
- Couples us to things which is pre- cemerick.piggieback/something (this was the problem with Figwheel, it didn't expose this!)
- Doesn't make it easy to use other things which hijack a session such as https://github.com/gfredericks/debug-repl
I think the problem is in two parts:
1 Creating a new session
- :Piggieback creates a new session inside the current normal session which is specific to Clojurescript
2 Choosing the correct session when valuating code
I think that maybe there should be more exposure of (2) somehow.
I made this the other day https://github.com/spacepluk/arcadia.nrepl
here it is in action with atom: https://www.youtube.com/watch?v=JbwMydnWUIk
I don't understand how I should manage sessions, so now I'm just blindly redirecting to the arcadia repl, any advice?
https://github.com/EwenG/replique/blob/master/README.md This seems interesting
@spacepluk the nrepl provides native session support, which you can clone, and every message with a unique id runs in isolation, with its out
@spacepluk you can clone it to create a new cljs session for example.
That replique looks really interesting considering the job api in neovim, I might try playing with that, for science!
I gather that replique has solved the socket repl tooling problem with a Lein plugin which loads the replique library
I guess it is okay as the library doesn't have dependencies that would pollute the classpath (and anyway, it could use name mangling like cider-nrepl and refactor-nrepl)
Should be useful for clojure-socketrepl.nvim