This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # babashka (46)
- # beginners (234)
- # bristol-clojurians (4)
- # cider (7)
- # clj-kondo (39)
- # cljdoc (8)
- # cljs-dev (10)
- # cljsjs (10)
- # cljsrn (24)
- # clojure (84)
- # clojure-brasil (7)
- # clojure-europe (12)
- # clojure-germany (4)
- # clojure-italy (3)
- # clojure-nl (41)
- # clojure-spec (17)
- # clojure-uk (66)
- # clojurescript (64)
- # conjure (161)
- # crux (18)
- # cursive (12)
- # data-science (45)
- # datomic (20)
- # devops (1)
- # docker (2)
- # duct (9)
- # events (7)
- # figwheel (1)
- # figwheel-main (20)
- # fulcro (32)
- # graalvm (5)
- # helix (82)
- # jackdaw (9)
- # jobs-discuss (19)
- # kaocha (11)
- # local-first-clojure (1)
- # malli (6)
- # meander (3)
- # nrepl (12)
- # off-topic (2)
- # other-lisps (15)
- # pathom (14)
- # rdf (6)
- # re-frame (8)
- # reactive (1)
- # reagent (5)
- # reitit (4)
- # rum (3)
- # shadow-cljs (77)
- # spacemacs (3)
- # sql (9)
- # test-check (31)
- # tools-deps (13)
- # vim (62)
Poll time! Who thinks Conjure develop is looking good and should be cut as a stable release, replacing the master branch? (🚀) And who thinks there's more to do before it's ready for day to day use, what do you need? (🛠️) Any beta testing right now is hugely appreciated! I want to know about glaring issues ASAP.
Once the main release is out it basically gives me time to focus on quality of life, bug fixes and features. I don't want to add extra things for the initial release because I want it to be viable and stable, so you can use it day to day while I work on more optional things in the background.
Perhaps I should just switch now - probably too late for testing and cutting a release?
If you want to make the switch I'd be more than happy to support you! Not that I think there's much to it, it's near enough exactly the same in many ways. It may be a rewrite but it still "smells" like Conjure.
I'd highly recommend it, it's working great for me! And the more people checking it out and giving me feedback the better. Especially your highly valued feedback 😄
I can walk you through it if you'd like, just give me a shout. The only thing I could see you having to actually mess with would be key mapping customisation, but the new system is quite nice (in my opinion) so it should be easy.
I should probably start another chat channel at some point that's not so tied to clojurians slack :thinking_face: I hate losing history here. Could do gitter or something eventually.
Yeah, there's no great solution. Gone are the days of IRC 😭 although we could always have an IRC home somewhere. I would just like something with infinite history and a client that doesn't grind my laptop to a halt.
I'm okay still being here all the time too, I just want to give people options to interact and ask questions.
Discord is decent but notifications are broken on iOS (at least they are for me). That's not a huge issue, though. And they're only broken inasmuch as they don't clear.
I like IRC just because it's so open but Discord is a good alternative that doesn't have some of the drawbacks of Slack.
I think I'll avoid changing the code for a little bit, just to let everyone test it (please try to break it). If you get the HUD or log into weird states or evals just stop working please let me know. Barring any showstoppers I think this will be the commit I release! Then I'll crack on with quality of life improvements, features and language clients! I'll re-share the poll for visibility.
I rarely use gitter - sometimes for spring stuff, but can't recall last time I was there.
Me neither, I'd just like some more options for people since I'm trying to open Conjure up to more languages. Having Clojurians Slack as the only place feels restrictive? Also Slack is a huge burden for me 😅 my poor CPU is always chugging with it open.
I press return a few times in the repl and I don't get a prompt back - now of course, this is not an issue with conjure, just nrepl, but is this observable by others?
You know in the log buffer, if you eval, the results goes to the end of the log, can something be considered so that it evals to the side? i.e.,
(+ 1 2) => 3
In the help, it says
":ConjureConfig [args] Displays or sets a configuration value with an optional language client prefix."
Reading it, I thought that by typing in
:ConjureConfig without args, would display all current configuration options as set
And not sure about displaying to the side :thinking_face: since it'll show the HUD to display the result anyway, food for thought though!
All of their values and defaults are in the help file. You can only see individual values or tables of values, so
:ConjureConfig mappings would show you all mappings. Maybe I can add a way to show all, it'll just be overwhelming, there's a lot.
In theory, they should all be set to the defaults that are in
:help conjure other than those you've set with your vim config
Yeah, I'll add a note for config visibility. Not sure how to solve it, but can find a way.
Why do you want to print all of it by the way? And would that include all language clients config too?
I was reading through the docs and whilst I could see each entry, I was wondering - just show me how it's all configured, right now.
what all the defaults have been set, with the overrides I've set (not that I've set any yet) in one place.
Yay! Glad to hear it. I'm mostly looking for anything that actually gets in the way of your work right now
Just a few finishing touches to feedback, then cut a stable release, then continue with polish and features for future releases.
It's reproduceable - if you open the log window, type something in (+ 1 2), then eval it, then cursor up and eval it again, you get the hud window appearing
If a result is appended to the end of the log and you don't currently have a log on your screen with the cursor following along, the HUD will appear (unless you've disabled it through config). This is to ensure you always see new entries, even if you're looking at something further up in the log.
Ah yes, I'll be changing that behaviour slightly soon. So the HUD will only show if you can't SEE the bottom of the log. Not if your cursor isn't on the last line
is there a quick mapping to close the buffer?, like in conjure having
I'll add it. Should it be EVERY log window (and the hud...) or should it be just the ones in your current tab :thinking_face:
i have run into a slight issue on the develop branch. i'm not sure if it's because of my setup or what, but it seems like when i use the "eval at mark" feature, it might be adding additional buffers or something?
i noticed that when i do "eval at mark," then i exit the buffer i jumped from via
:x or similar, there seems to be another copy of that buffer underneath
i can't figure out how to reliably repro it, unfortunately. i tried again now and no dice
That's suuuuper weird. So you closed the window, but it was then still open? The only thing I can think of is absolute and relative paths for the buffer, but I'm pretty sure neovim uses a canonical path for each buffer.
So if you have a file open, it's only open once in one buffer. You can't have the same file open twice (afaik).
So if you have foo.clj open and you do :e foo.clj, it'll open that same buffer, not another one.
i'll keep an eye out for the next time the problem occurs, and see if i can gather more information
Hmmm yeah, seems SUPER weird to me. Like how Nate (I think) got the HUD stuck open, I haven't seen that in months months since I first wrote it. If there's elusive bugs out there, I wanna squish em. Everything happens in one thread which makes timing issues and race conditions a lot less frequent, but they could still happen. Some things require a callback. If I'm holding onto some state via closure across a callback and that state is then out of sync, it can cause timing bugs.
Weird! I'll make a note to read the code and see if I can spot any way it could happen
I’ve just started playing with conjure with a simple duct project. It is using lein + integrant and I was wondering if it is possible to use something like cider-refresh in conjure. I’ve just stumbled on this gist from the Conjure’s author but prepared for vim-fireplace https://gist.github.com/Olical/1c696c01ed573f1844a97b047aba30f3
Oh yeah, that's me! It's actually built into the develop branch, you can hit your prefix key (<localleader> by default) and rr to refresh the changed namespaces.
Check out :help conjure-client-clojure-nrepl and grep for refresh, there's options in there that let you set the before, after and dirs too!
Thanks, I will try it. Now I am having issues connecting the lein repl with conjure. I’ll try to investigate a bit more.
Oh odd, like it doesn't automatically connect? Might not be writing the .nrepl-port file?
The .nrepl-port file exists, and it seems conjure connects to the repl but when a try to evaluate a simple form in a project file it logs>:
eval (root-form): (inc 5)
(err) Syntax error compiling at (example.clj:16:1).
(err) Unable to resolve symbol: inc in this context
That's probably to do with your namespace not being loaded yet :thinking_face: so you haven't evaled the ns form, which means when I swap to it with
in-ns for you it doesn't have Clojure required.
<localleader> ra did the trick. I presupposed I could run core functions without loading first the project namespaces.
By they way, I also tried to set clojure.nrepl/refresh.after and clojure.nrepl/refresh.before configurations to reload integrant components and it looks like it is working. Thanks!
RE cider-refresh: @olical please still the code from replant to auto-detect the start/stop functions. I use it every day and managed to stop thinking about it.
Ah good idea, had a vague notion of this on my roadmap already but was scared of it doing the wrong thing