00:32 <fiddlerwoaroof> I'd suggest the first message be a string literal

00:33 <fiddlerwoaroof> That way it can be read with a JSON parser or a lisp parser

00:33 <fiddlerwoaroof> (If the goal is to support other serialization formats)

00:33 <fiddlerwoaroof> Anyways, I've been wondering, does slime have hooks for "smarter" completions?

00:34 <fiddlerwoaroof> I'd like to be able to customize the completions so that (ql:quickload :<TAB>) shows me a list of quicklisp packages.

00:34 <fiddlerwoaroof> s/packages/systems/

00:34 <fiddlerwoaroof> (in-package :<TAB> could show a list of valid packages, etc...

01:15 <fiddlerwoaroof> Something like this sort of works: https://github.com/fiddlerwoaroof/slime/commit/d7541ed676e99650c555db8b105c577efade7946

01:16 <fiddlerwoaroof> The basic idea I have would be to add a context parameter to the various completion fucntions in elisp/cl

01:16 <fiddlerwoaroof> Then turn SWANK::FUZZY-GENERATE-MATCHINGS into a generic function and specialize it on the context parameter in user code

10:17 <luis> flip214: yes, you need to change the multithreaded swank so it doesn't do that for the first message.

10:18 <luis> fiddlerwoaroof: there may be something like that in SLIME, I seem to recall being able to tab complete pathnames, for instance.

10:18 <luis> fiddlerwoaroof: in any case, that's a great idea.

19:12 <fiddlerwoaroof> What I'm not entirely sure about, is how to reliably detect the first element of the current form when input is not complete

19:21 <scymtym> eclector is probably not an acceptable dependency, but if it was, you could READ with automatic error recovery. that gives reasonable results in most cases, in particular for things like missing closing parenthesis

21:41 <scymtym> fiddlerwoaroof: https://github.com/yitzchak/common-lisp-jupyter/blob/master/src/cl-jupyter/parser.lisp and https://github.com/yitzchak/common-lisp-jupyter/blob/master/src/cl-jupyter/complete.lisp may also be relevant (apologies if you already know about those)

22:15 <luis> We should definitely get eclector into SLIME at some point, perhaps under a different package name to avoid collision with other eclector uses. Lots of fun stuff that could be done with a nice reader.