This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-09
Channels
- # announcements (1)
- # aws-lambda (3)
- # babashka (6)
- # beginners (91)
- # bristol-clojurians (5)
- # calva (25)
- # chlorine-clover (8)
- # cider (6)
- # clj-kondo (13)
- # cljdoc (10)
- # cljsrn (1)
- # clojure (80)
- # clojure-berlin (6)
- # clojure-europe (29)
- # clojure-nl (4)
- # clojure-spec (18)
- # clojure-uk (51)
- # clojurescript (41)
- # conjure (55)
- # cursive (3)
- # datomic (58)
- # emacs (9)
- # events (1)
- # figwheel-main (2)
- # fulcro (29)
- # graphql (12)
- # helix (4)
- # jobs (4)
- # klipse (8)
- # london-clojurians (1)
- # malli (5)
- # off-topic (13)
- # portal (9)
- # re-frame (30)
- # shadow-cljs (44)
- # spacemacs (7)
- # specter (3)
- # sql (11)
- # tools-deps (71)
- # windows (1)
- # xtdb (10)
One thing I noticed about the new release v4.4.0 is this. Let's say I open up vim and I open a file to edit. Conjure correctly says ""no nRepl port file found." I then launch a repl. Correctly, if I eval the buffer using ,eb
, conjure will now connect and attached to the "assumed" session.
However, the buffer won't be eval'ed. I have to then do ,eb
again to eval the buffer completely.
Should it be like that? Perhaps on connection it should automatically eval the buffer too?
It should try to eval, realise it doesn't have a connection, connect and THEN continue the eval. That's how it worked during development.
Ah, it looks like if it's your first connection to that REPL it doesn't work? On the second connection it works fine for me.
I haven't been going outside much at all over the recent months, but I've been wearing masks whenever I've had to.
i always get a little bit jealous when people mention doing work on the train. i wish public transit was decent enough in my part of the world that i could take the train everywhere and have a little productivity time in the process!
i'm able to take the train from city to city in the triangle (central NC), but driving is the norm once you get to the city, so that sort of forces you to drive everywhere anyway
Hey @olical is possible that the auto-connect is doing a eval auto-require? Because, auto require doesn't work for me and when I try to evaluate a file disconnected I have the same problem I would have if I had the auto require on.
Hmm nothing new around this, post connection auto require has always been a thing to avoid nREPL complaining about namespaces not existing
You can turn off auto require if you haven't already? Or you've turned it off and now it's not working?
It's off, but when I do a eval on a disconnected buffer it behaves as it was on
:thinking_face: I'm really sorry about the inconsistency, I didn't add anything new here so nothing comes to mind, so I guess it's a bug somehow, I'll have a look into this ASAP.
Interestingly some of my REPLs don't like being started up then auto connected to with like "eval file"
But if I boot the REPL, give it a little while to start up, connect, then eval it's fine
So it's almost like firing a bunch of code at a REPL just after it started and you connected can break it?
I will test a little bit more