This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-17
Channels
- # announcements (2)
- # aws (44)
- # beginners (96)
- # calva (10)
- # cider (7)
- # cljdoc (5)
- # cljsrn (2)
- # clojure (38)
- # clojure-dev (19)
- # clojure-europe (6)
- # clojure-italy (16)
- # clojure-nl (10)
- # clojure-norway (44)
- # clojure-spec (7)
- # clojure-uk (74)
- # clojurescript (133)
- # cloverage (1)
- # cursive (54)
- # datomic (78)
- # duct (11)
- # graalvm (5)
- # instaparse (4)
- # joker (3)
- # kaocha (5)
- # nrepl (2)
- # off-topic (10)
- # pathom (56)
- # pedestal (1)
- # reagent (7)
- # reitit (17)
- # shadow-cljs (144)
- # slack-help (2)
- # sql (35)
- # testing (5)
- # tools-deps (22)
- # vim (22)
- # xtdb (11)
@clojurians-slack100 @martinklepsch are you using vim-clojure-highlight? I'm thinking I might fork it into clojure-vim, but I'd like to have someone who's actively using it who will fix things as they encounter them.
(I'd also extend push rights to the author of the currently working fork, I just can't remember their slack username!)
I have it installed but Iβm not sure if itβs doing anything lol
I think there's something broken on the current fork that mostly works, @clojurians-slack100 had a tweak to get it working..
@dominicm I only learned about it a few days ago when it was discussed in here. I'm using it day-to-day, but I consider it still in a "trying it out" phase. So far, on the smallish projects I've been working on lately, it has been quite helpful. But didn't someone also mention that it adds quite a delay on larger projects? If that's the case, it may (unfortunately) not stay in my init.vim
. While I'm using it, I don't mind having a look at issues that I encounter, but I'm no VimL expert, and I usually approach these things by weighing time invested against need/urgency/usefulness.
Btw, the fix I mentioned is in my comment on the PR: https://github.com/guns/vim-clojure-highlight/pull/7. I.e. it's applicable to jrdoane/vim-clojure-highlight and not guns/vim-clojure-highlight
@clojurians-slack100 I was hoping someone might take interest in adding async support π
https://github.com/clojure-vim/async-clj-highlight?organization=clojure-vim&organization=clojure-vim clojure-vim already has an async fork π I don't think it works with fireplace though
thinking about it, vim-clojure-highlight might be the wrong approach to take. cider-nrepl has something to query the state.
not documented well, but it's called track-state https://github.com/clojure-emacs/cider-nrepl/blob/107e376ef3f294161dc2aea42b213889f3f05c26/src/cider/nrepl/middleware/track_state.clj
IMHO, the "best" approach to adding Clojure IDE functionality to vim, is fireplace (or something similar) + CIDER via nrepl, because of the much better established tools on the CIDER/Emacs side. So I prefer using CIDER stuff over pure vim plugins, like you're suggesting @dominicm