This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-06
Channels
- # announcements (3)
- # aws (23)
- # beginners (61)
- # calva (57)
- # cider (121)
- # clara (1)
- # clj-kondo (9)
- # cljs-dev (62)
- # cljsrn (3)
- # clojure (79)
- # clojure-europe (2)
- # clojure-nl (19)
- # clojure-spec (9)
- # clojure-uk (14)
- # clojurescript (92)
- # clojureverse-ops (2)
- # cursive (3)
- # data-science (2)
- # duct (1)
- # figwheel (2)
- # graphql (6)
- # jobs (1)
- # kaocha (5)
- # leiningen (11)
- # off-topic (25)
- # overtone (1)
- # pedestal (4)
- # portkey (1)
- # re-frame (1)
- # remote-jobs (2)
- # shadow-cljs (179)
- # slack-help (3)
- # specter (7)
- # testing (14)
- # tools-deps (14)
- # unrepl (12)
- # vim (2)
- # yada (3)
@pez: figured out the tools.reader problem. Our project had a super-old version of tools-reader. I upgraded that, and no need for exclusions.
I started to think a bit about that actually and wondered if maybe such settings are better handled in the project definitions than in jack-in injections. But, yeah, even better to not include super-old ones 😃
I just installed calva extensions on a relatively clean vscode 1.33.1 (no other exts except for golang)
looks like syntax highlighting for clojure and clsj is broken - does not highlight keywords, punctuation etc.
I'm using the default vscode theme and don't see any errors in the logs so I'm puzzled as to why no highlighting
my guess is that vscode uses some default highlight mode and manages to find "keywords" (aka special forms) and basic literals
but no clojure specific highlighting at all, keywords (:like-that) stay the same color as the rest
This should fix keywords for you: https://github.com/BetterThanTomorrow/calva/wiki/Customising-Calva#keyword-highlighting
I am unsure about what else you are missing. So don't know if something is wrong or maybe just not implemented.
No worries. This channel is your friend either if it is you or I who have missed something. 😃 And I should probably make that a bit more visible...
Here's a new dev build of Calva 2, I'd like help with testing. Added since last build is: 1. Jack-in starts with asking you about project types it think matches and if Figwheel or Figwheel Main should be started. 2. Jack-in opens the browser for you after having started Figwheel (like Fighweel Main does by itself). 3. Jack-in does not inject CLJS dependencies unless you have asked it to start CLJS things. Also the REPL window indicates REPL type (CLJ or CLJS) a bit clearer and for Leiningen and shadow-cljs you even get some more visual clues. Thanks in advance for help with testing it!
as in, when I jack-in with Cider, and I call (reset)
Cider will report that the it failed
The REPL window binds some keys so might be it hangs and doesn't update the context so that the editor can bind them... If so we can probably make that a bit more robust by updating the context on some editor event.
With some luck this is the same problem as with the cljs repl hanging on println. But I am seldom lucky with these things. I guess my luck in love grabbed my full share of luck.
is there anything I need to configure to have #_(form...)
displayed similar to ; (form ...)
?
There is nothing you can configure for that, unfortunately. If you're good with regexps you can pick up my branch where I try to fix this, though. I spent quiet some time with it, but got stuck on something, don't remember what right now.
Here’s the branch: https://github.com/BetterThanTomorrow/calva/tree/wip/grammar-comment-expression . I just merged latest dev
on top of it.
I will return to it eventually, @claudiu, but it will take a while before I can prioritize it.
I was aiming a bit higher then merely ;
, though. I wanted to make it syntax highlight as regular code, but just add italics to it so you could see it was disabled.
thank you 🙂 Need to finish up a freelance project this week and the will try to play with it a bit. Not sure I can solve it (just installed vs code for the first time this week) , but could be fun for learning and getting the hang of things 😄
Cool. I will be hoping you find some time for it. It is more TextMate rules and regexp than vscode really. Holler my way when you want to take a look at it and I’ll try to remember how it worked.