14:36 <luis> Do we want to use github.com/slime/slime's new Discussion feature? Beats discussing using issues, maybe. Very few people seem to use mailing lists these days, sadly.

14:38 <jackdaniel> huh, githubd! github discussions, one could have thought that the "d" stands for "distributed" :-)

16:05 <flip214> github _daemon_

16:06 <flip214> luis: any opinion about JSON support in slime? I asked here on Nov 28th... of course I can copy/paste again for your convenience, but in case you have a scrollback I wouldn't need to

16:08 <luis> flip214: in SWANK, you mean? Yeah, we probably should add it in somehow for VIM (apparently), and VS Code and things like that. Not sure what the best way to do it is. Do share your ideas.

16:09 <Shinmera> I've been using PLNs a lot and is this just my setup, or does slime's completion not work right with that?

16:09 <luis> (reading the scrollback)

16:09 <luis> Shinmera: what are PLNs?

16:09 <Shinmera> package-local-nicknames

16:11 <flip214> luis: the main issue is that I need to add _auto-detection_, as in a multi-threaded connection the read loop already fetches the next packet while the command to switch to JSON is being processed.

16:12 <flip214> Or I need to use a alist of (initial-character . parse-fn) that gets changed while being in the reader - which isn't nice either

16:12 <luis> Shinmera: I don't know, I've never used them much.

16:12 <luis> flip214: can't we have an start-server option to pick the message format?

16:23 <luis> i.e., can't we pick the message format when starting the swank server?

16:24 <flip214> is auto-detect on #\( vs. #\[ a problem?

16:24 <flip214> I'd like to have one swank server being able to support multiple clients, with a per-connection encoding

16:25 <flip214> so per-server isn't that nice

18:29 <luis> flip214: I see. We could change the protocol so that there's an initial setup message. We could probably even be backwards compatible by being permissive about that message missing, but backwards compatibility is not really a concern. Such a setup message would be an important step in being able to e.g. version the swank protocol, so that could

18:29 <luis> have other uses.

18:30 <luis> flip214: the first message could be (hello :format :sexp/:json) or something like that.

18:31 <luis> flip214: but your auto-detection idea works too 🤷‍♂️

19:43 <flip214> luis: I *tried* having a first message to switch to JSON.

19:44 <flip214> but the reader for a multithreaded swank gets to reading _immediately_ again, and so a passed-in argument for the parse fn is outdated already!

19:46 <flip214> see https://github.com/vlime/slime, btw