Conversation

oh, I should replace eval-buffer with the custom version I made (because eval-buffer really, really wants to parse for the lexical-binding variable) first, before I forget

now I can pull documentation for non-elisp functions and variables! that wasn’t as painful as I’d feared, for eldoc and helpful at least. there’s probably a bit more patching to go, this is the one part that feels fragile because it defines advice across a couple other packages I don’t control

anyway I should do that eval-buffer replacement huh!