This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-28
Channels
- # announcements (12)
- # babashka (87)
- # beginners (84)
- # calva (22)
- # circleci (4)
- # clj-kondo (46)
- # cljdoc (6)
- # cljsrn (15)
- # clojure (87)
- # clojure-europe (18)
- # clojure-uk (7)
- # clojurescript (20)
- # community-development (3)
- # conjure (1)
- # cursive (13)
- # datomic (14)
- # events (7)
- # fulcro (27)
- # graphql (31)
- # helix (8)
- # jobs-discuss (1)
- # lsp (43)
- # malli (11)
- # meander (64)
- # off-topic (7)
- # pathom (26)
- # polylith (9)
- # practicalli (2)
- # re-frame (33)
- # reagent (2)
- # reitit (5)
- # releases (2)
- # rewrite-clj (2)
- # shadow-cljs (69)
- # specter (5)
- # sql (1)
- # tools-deps (85)
- # tree-sitter (1)
- # vim (3)
You can see what encoding is being used for the given file in the status bar (this is a VSCode feature), and you can click it and select to reopen a file with a specific encoding, or save with a specific encoding. I'm not sure if that's helpful to you.
every time I started in command line with deps.edn
with :dev {:jvm-opts ["-Dclojure.server.repl={:port,5556,:accept,clojure.core.server/repl}" "-Dfile.encoding=\"UTF-8\""]}
to java start in UTF-8 mode. But I see that Jack-in
I can´t include this file.encoding="UTF-8"
I think you can use https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/envvars002.html for that.
Is it possible to restart lsp? I’ve the lsp config file modified, but I don’t want to close vscode and restart.
One of the problems I’m having with Vim is that Forward Sexp doesn’t respect visual mode. For example if I go to the end of a form, it gets stuck unless I put it in insert mode after the parenthesis before doing another Forward Sexp. Any ideas?
No ideas, really. Calva would need to know about visual mode to be able to know what is the right thing to do.
Also wondering how do you toggle paredit mode? I was thinking about disabling it so I can keep Calva for the REPL and other features, then using something else like parinfer-rust through the VS Code Neovim extension to get some paredit-like functionality
Paredit and parinfer should be quite compatible. I don't think disabling paredit will gain you anything. What you probably will need to disable is Calva's autoformatting.
This is what I mean by disable paredit mode. I see it in the manual here https://calva.io/paredit/ but can’t find how to actually do it in VS Code
Oops nevermind I found it "calva.paredit.defaultKeyMap": "none"
it was on that page after all, at the bottom
Hello all, is there any way to refresh tests from a namespace, if I remove one test, how can I remove that test is not use anymore?
The only way I know to do it, besides restarting your repl, is to redefine the var that the test was assigned to. So if you removed a test called some-test
then evaluating (def some-test nil)
in the same namespace would make that deleted test not run any more.
This is not a great solution though, of course 😄. I'd recommend restarting your repl, unless anyone else knows a better way. CC @U0ETXRFEW