Speaking of the blob and its build task

each time one submits the blob, it gensyms everything; I think it could be simplified so that gensymming only occurs at build time. There’s no point gensyming at each use, is there?

I thought about that as well.. and to be honest I thought there was a reason beyond my comprehension at the moment

but I don't see why not to doit at build time

reasons that may have influenced me was: ns removal on deconnection, one ns per session and global state (no rotten tomatoes thx)

hmm global state could be a thing

we should check and make it indexed per session

we still haven't address the global settings problem: being able to change settings in user conn from aux conn

that could work

global settings: for the record my proposal was to settings per “printing context” and have a reference to the origin printing context in elisions

hey folks, particularly @volrath I think, I am having trouble with unrepl.el, running M-x unrepl-connect in a leiningen project - after a while, I see

;; Waiting on UNREPL... 

connection broken by remote peer

@cgrand would you include there`*realize-on-print*`?

@j0ni that seems like unrepl.el is not able to run the project

@volrath yes

ahh, now, I just tried lein repl in the project and it timed out, so yeah, I think a different problem here

@volrath thanks and sorry for noise

@j0ni np, let me know if you get it to work

or not 😉

@cgrand that sounds good to me.. and just to make sure, you would index those settings-per-printing-context into sessions, right?

yes

cool 🙂

well, my next milestone is to get some integration tests going on for unrepl.el, after that I could help with some of this discussion if it's still reasonable 🙂

between work, chicken pox outbreak and incoming santa, time is tight atm for me

noted, hopefully I'll have some time between 24 and 31

does unrepl.el pay attention to leiningen :repl-options?

btw, in a complete different topic.. I've been thinking a lot on a new name for unrepl.el

I don't have a clear candidate yet, and I accept suggestions 😉

@j0ni tbh, I don't know with 100% certainty at the moment, but I'm inclined to say that it doesn't

@j0ni I think you're experiencing an unrepl.el bug, I tried with a lein project I used to test and I'm getting your same problem

I call the umpteenth Naming Game open!

unrav.el 😉

uncider (I need to get going)

@cgrand hahahaha

aha @volrath cool!

looks like the repl command sets the port to 0 - does that have special semantics?

lein   trampoline run -m clojure.main -e "(do (require 'clojure.core.server) (let [srv (clojure.core.server/start-server {:name :repl :port 0 :accept 'clojure.core.server/repl})] (println (pr-str [:unrepl.el/server-ready (.getLocalPort srv)]))))" 

yeah, that only generates a random port, but the problem is right there

is not daemonizing the socket server

ahh

sorry, it's not stopping the daemonization

unreel

unriddle

@j0ni that last commit should fix the problem

sweet, I will pull that now

@cgrand I was actually thinking on breaking the "un-something" pattern... would I be banned from this channel if I proceed? 😳

do you have a theme, a sound or whatever to guide us?

fwiw I like the counter-cultural vibe that un* evokes

I was thinking on the idea of looping, naming it after something that evokes looping

Loftstrom 😉

(a loop to go to space)

ooh, that reminds me, I registered like 4 years ago or something, I will donate it to worthy not-for-profit schemes 😄

not bad!

haha good @j0ni

btw, did the commit fix your problem?

w00t yep

thanks for reporting

amen or amenbreak

GOTO

amen as in the new testament? not a fan..

groundhog as in Groundhog Day — quite a loop

hey I like this one, easy on a mascot if you need one etc.

haha

escher obviously when it comes to loops

mobius

@volrath do you intend to add code navigation features a la cider? I can get some of the way there with dumb-jump, but diving into code inside dependency jars doesn't work

ouroboros but I’d like to use it one day

munchhausen

@cgrand I thought of escher but I've seen it as the name for other stuff

@j0ni yes, I'd like to add that feature, I use it in cider as well

I give up for now but my fav is groundhog by a huge margin

I'm thinking on spiral, I like it cause it's simple, short, easy to remember, and it's an ever expanding loop... but i also like loftstrom

loftstrom is heavy on typo but easy on search

yep

there's also a clojure spiral lib, but there's no emacs spiral

helix

I like loftstrom

spirepl

spiroloop

sriral is cool

In the same vein you can consider flux and maelstrom perhaps

I recall in the past someone had suggested clint (clojure interaction), which was kind of cool as well

the potential for clint-load and clint-reload is epic 😄

But reminds of linting tools

yeah, I know that originally someone thought of naming eastwood clint, but it sounded too quaint.

Maybe hammock in honour of Rich?

Or havoc to sound more cool?

I like spiral

I like maelstrom as well 🙂

also maybe just strom, out of maelstrom and loftstrom

but I feel like it might be typo'd into storm often

True that.

@volrath I can't get unrepl-eval-buffer to work. Each time it try I get:

Unhandled aux exception localhost:5555 No such file or directory 12

ström can be spelt stroem when you can’t type the umlaut no?

@adamfrey huh... that's a first for me, let me try to reproduce

@cgrand I like that

Then add a a and go for the anagram maestro :-)

@adamfrey you used unrepl-connect-to?

actually just unrepl-connect, and it set me up with lein

I just tried again with a terminal socket server and unrepl-connect-to and I get the same

hmm weird, can't reproduce

do you see a [localhost:<port>] in your modeline?

yes

is it localhost:5555? if so, is that the same port as your running repl?

it's the same

ah... nvm, I remember what that is..

I'm in the middle of reworking exceptions that come from evaluating whole buffers... when an exception occurs while eval-ing a buffer, I want to show that exception in the REPL buffer, but I also want to show a small overlay with the offending line in the working buffer

I don't have it ready yet, but that error that you're seeing means that the evaluation returned an exception

so there's something in the buffer that's causing a REPL exception

ok, I'll try a different namespace

yeah sorry about that

no problem

unpirel ?

just wanted something with un in front, el at the end and repl somewhere 😄