This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-08
Channels
- # announcements (40)
- # babashka (14)
- # babashka-sci-dev (7)
- # beginners (50)
- # calva (8)
- # cider (25)
- # clj-kondo (7)
- # cljdoc (8)
- # cljs-dev (14)
- # clojars (6)
- # clojure (56)
- # clojure-australia (1)
- # clojure-berlin (2)
- # clojure-dev (16)
- # clojure-europe (18)
- # clojure-nl (1)
- # clojure-norway (5)
- # clojure-uk (7)
- # clojurescript (100)
- # cursive (57)
- # data-science (9)
- # datomic (6)
- # emacs (11)
- # figwheel (2)
- # fulcro (14)
- # helix (2)
- # hyperfiddle (9)
- # introduce-yourself (1)
- # lsp (20)
- # malli (14)
- # meander (34)
- # minecraft (1)
- # missionary (8)
- # off-topic (37)
- # pedestal (4)
- # polylith (18)
- # portal (3)
- # re-frame (5)
- # ring (33)
- # shadow-cljs (32)
- # spacemacs (6)
- # vim (16)
does anyone else have this problem with vim? I use vim-sexp
and when I open a quote it adds the close as expected, but when I close the quote it adds a whole new set. e.g.:
"typing xxx
"typing xxx "" "
I see the same in my nvim. I have narrowed it down to treesitter. When it is enabled it removes the old regex based highlights. Looks like vim-sexp depends on those highlights to understand that cursor is inside a string.
looks like adding "clojure"
to the highlight.additional_vim_regex_highlighting
in treesitter config setup fixes the vim-sexp
oh wow, that does the trick! Have you reported this to either project?
Ah. Well good find. You saved me a lot of pain (that I've been dealing with for quite some time)
@alex.sheluchin if you want to debug coc.nvim, change the trace to be "verbose"
and then you can check messages with :CocCommand workspace.showOutput
there's other stuff you can do but that's a good first step
will show you pretty-printed json values passed back and forth with clojure-lsp
Thank you, @UEENNMX0T. That helped me figure it out. It wasn't outputting anything at all which lead me to understand that it wasn't using coc.nvim to pull up the documentation. vim-iced was providing it.
Good catch!
This has got to be FAQ (and maybe if I knew where to look it would be easy to find the answer 🙂 ), but so far I haven't found an answer. When running Conjure with conjure-client-clojure-nrepl, when it connects, there is a session name. That suggests that it would be possible to run multiple nrepl sessions. For example, it would be nice to put code that runs for a long time into one session, and then use another session to continue to evaluate other code, or use other features of Conjure, while it's running. (Of course I could just run the slow code somewhere else, but it's convenient to do everything from one nvim instance.) Where should I look for information on creating multiple sessions? Is this in the Conjure docs somewhere (I haven't found it). Or do I need to learn more about nrepl?
Session mappings can be found here https://github.com/Olical/conjure/blob/a8686aa6f8760bd3cd4f219a8a4101af037c9d9b/doc/conjure-client-clojure-nrepl.txt#L108-L122
Thanks @U38J3881W! I don't know how I missed that.
What does cloning a session mean? Does that mean that the environment is copied over? And a fresh session just has the environment from project.clj (in Leiningen)? And I assume that "Assume the next/previous session" means that further interactions will go to that session--is that right? My guess is that the answer to all of these questions is "Yes".