Right now plugin host simply looks for .lisp files in rplugin/lisp/ directories. This works for trivial plugins such as the sample plugin, but is probably also not the way to go for more complex ones. I think for more complex plugins cl-neovim should support looking for (and requiring) .asd files instead.
There is also still a question about using quicklisp to handle loading of dependencies/plugins. On one hand this introduces a pretty substantial lag when loading up lisp host, but on the other hand it makes everything really convenient for end user.
Right now plugin host simply looks for .lisp files in rplugin/lisp/ directories. This works for trivial plugins such as the sample plugin, but is probably also not the way to go for more complex ones. I think for more complex plugins cl-neovim should support looking for (and requiring) .asd files instead.
There is also still a question about using quicklisp to handle loading of dependencies/plugins. On one hand this introduces a pretty substantial lag when loading up lisp host, but on the other hand it makes everything really convenient for end user.