IRC channel logs
2026-08-14.log
back to list of logs
<stdh>Hoot question: do i understand correctly that the --repl-port part (listening for repl clients) of `hoot serve` doesn't really work? IIUC the function handle-repl in web-server.scm:386 always errors out because control-ch is #f. <stdh>I was trying this out for professor hoot and wondering where exactly in the application I would end up if i connected to the repl-port. Turns out the answer is 'node'. :) <stdh>also, i have a very small patch to improve cli argument handling. shall i make pull request for that? <dthompson>stdh: the repl port stuff works. I wrote and have used it. <dthompson>it's intended for interfacing with a repl running in the web browser <dthompson>importantly, a repl that can act as a *server*. (hoot repl) is not a server. <dthompson>regarding cli argument handling, sure make a PR and I'll take a look! <dthompson>it might take me a bit because I'm technically in vacation mode <dthompson>but if it's small then it will be easy to take a quick look :) <stdh>the patch is very small, you can review it before the boss knows you're working on vacation time ;) <stdh>for the repl itself, it seems i have some more digging to do, i'll start with the documentation that i skimmed over... <dthompson>the feature is new and somewhat under baked so it's not the best experience yet <dthompson>but the reason for the hoop jumping is that a web browser is strictly a client, not a srever <dthompson>so in order to connect to a repl running in the browser in the terminal (or emacs) you need to run a proxy to act as middleman <dthompson>perhaps your experience can be a guide as to what the docs should actually say to make this easier to understand <stdh>yes, i think the docs could be improved. but it's good to know all moving parts are there, i just didn't tape them together correctly. <stdh>(it would be very weird that an announced feature isn't working because of missing parts, spritely is no llm sloperation after all)