This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-30
Channels
- # aws (4)
- # beginners (143)
- # boot (37)
- # cider (31)
- # cljs-dev (53)
- # clojure (303)
- # clojure-conj (5)
- # clojure-dev (106)
- # clojure-dusseldorf (2)
- # clojure-greece (3)
- # clojure-italy (23)
- # clojure-spec (83)
- # clojure-uk (7)
- # clojurescript (328)
- # core-async (25)
- # cursive (2)
- # datascript (2)
- # datomic (3)
- # emacs (10)
- # hoplon (1)
- # jobs (2)
- # lein-figwheel (1)
- # leiningen (13)
- # luminus (6)
- # off-topic (38)
- # onyx (2)
- # parinfer (13)
- # pedestal (2)
- # portkey (5)
- # re-frame (11)
- # reagent (2)
- # shadow-cljs (61)
- # specter (6)
- # unrepl (60)
- # vim (4)
@kotarak @volrath @pesterhazy is there any sense to define a common complete
action then? (yes I can take the union of what all of us are doing)
I feel it's not needed in unrepl. this type of thing fits better in something like orchard
Maybe. I could live with the transforming the input on the client side into the required vim format.
However that would be slower and bans me from adding possibly not contained information.
Whether this is hidden behind a commonly defined action or whether it's my own doesn't really matter, does it?
Having a common action would then mean, however, that only what goes in would be specified. The output would obviously differ.
Vim needs a map contain this and that key. Emacs requires a list. IntelliJ takes ......
And whether I have a local action mapping system or the one we have at the unrepl side now doesn't really matter.
yeah but my hope was that tools author would have basic intreaction ok without having to write custom actions for each taregt
Hmm.. Since I have no clue about ClojureScript, that was not my concern. I see the problem more on the client side. That each client has its own requirements and interfaces.
(Eg. the completion in vimpire is actually voodoo. Normally the interface is syncronuous. And they do some black magic to make it asyncronuous. Otherwise I wouldn't be able to provide completion, because the connection is async.)
Shading with find & replace failure:
(ns compliment.core$lGKpTGw5kbRXJ4kBA9SDwnNAxCE
"Core namespace. Most interactions with Compliment should happen
through functions defined here."
(:require (compliment.sources$p8UbKISrPlDh$sMwHBsmdzBLjpU ns-mappings
namespaces-and-classes
class-members
keywords
special-forms
local-bindings
resources)
[compliment.sources$p8UbKISrPlDh$sMwHBsmdzBLjpU :refer [all-sources]]
[compliment.context$50K5FJhtgeO$CW7edfPjhgFPlr8 :refer [cache-context]]
[compliment.utils$YmBUUrJwullK9KE0yVCYElF$2Xk :refer [*extra-metadata*]]
[clojure.string :refer [join]])
(:import java.util.Comparator))
The prefix gets shaded instead of the full namespacesI'm not sure if this was noticed amongst the spec conversation: https://github.com/athos/spectrace/blob/master/README.md