23:13:17Baggersaw I'm looking forward to seeing more from that. I miss the old treehouse streams.. even if I did miss a bunch of them by not turning up :/
23:25:44Baggersdamn I gotta run. I'll come bug Shin another day. Gdnight folks
6:39:33fiddlerwoaroofShinmera: I've noticed that (lquery:$ (inline "...")) behaves kinda badly
6:39:44fiddlerwoaroofEspecially if the string is long
6:40:27fiddlerwoaroofI realize that it's supposed to be a plump dom object, but the current behavior is kinda surprising
6:43:12fiddlerwoaroof(lquery:$ (inline "<a>")) right now just kinda hangs and eats up cpu and memory until you run out of heap space
6:44:16fiddlerwoaroofIt would be nice if lquery would notice something is wrong and complain
6:46:39malmShinmera: https://plaster.tymoon.eu/view/1102#1103 <-- internal-uri returned an empty domain. I assume that's what you wanted to verify right?
7:22:37ShinmeraYes, but that's not from plump, that's from CLSS
7:22:58Shinmera(lquery:$ (inline "a")) is the same as (lquery:$ "a")
7:23:33fiddlerwoaroofAh, what I was trying to say was that (lquery:$ (inline (plump:parse "<a>"))) works the way I expect things to work
7:23:34Shinmeraso "<a>" is being treated as a selector
7:23:47Shinmerait still shouldn't infinite loop of course
7:23:51fiddlerwoaroofbut if I forget and do (lquery:$ (inline "<a>")), everything blows up
7:24:37fiddlerwoaroofI guess I didn't fully understand what inline was supposed to do, though: I've always thought of it as "the way you pass a pre-parsed document to lquery"
7:25:55ShinmeraThe documentation says: Treats the form as if the evaluated value was put literally in place.
7:26:11Shinmeranot sure how it could be any clearer
7:26:59fiddlerwoaroofYeah, I've been using lquery for a while, so I'm working off memory